On Tue, 27 Dec 2022 16:50:54 -0800 (PST)
JD Allen <[email protected]> wrote:
> When I run it with clean: vim --clean -p file1 file2, I don't get the
> error. Does that mean its a plugin problem?
Possibly. '--clean' argument tells Vim not to load your personal config
(read ':h --clean'). So if you can't reproduce the issue without
loading your personal config, that means the problem is caused by
something in your personal config. Whether it's a plugin (something
someone else wrote) or something you wrote in your vimrc, cannot be
guessed without further information. Debug your personal config [1] and
find the source of the issue.
> Yes, the files in question show up in .viminfo several times.
> What should I do next?
Read ':h viminfo'. I am not 100% sure, but it seems you opened the
files file1 and file2 sometime ago and the state of the buffers were
recorded in viminfo file the last time you quit them. And Vim is now
trying to open those files exactly how you quit them the last time,
after reading the state from viminfo file. But somehow the files have
changed in the meantime, and the lines 3467-3470 do not exist anymore,
which is causing Vim to lose its cool, because it had saved some state
information in the viminfo file -- states associated with those lines,
states which Vim can't reconcile anymore with the associated lines.
My uneducated suggestion would be to remove all lines from '~/.viminfo'
which contain mention of file1 and file2. REMEMBER to BACKUP viminfo.
^^^^^^^^^^^^^^^^^^^^^^^^^^
[1]: https://vi.stackexchange.com/questions/2003/how-do-i-debug-my-vimrc-file
--
Enan
[email protected]
https://git.sr.ht/~enan/
https://www.github.com/3N4N
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20221229001421.000029d1%40gmail.com.
