On Tue, Dec 12, 2023 at 03:00:51PM +0100, y...@vienna.at wrote: > * What exactly did you do > Starting vim > > (or not do) > not using nano? > > that was effective (or > ineffective)? > Starting was enough > > * What was the outcome of this action? > the srring I sent > > * What outcome did you expect instead? > No nonsence
Something got your viminfo file into an unexpected state, which Vim is warning you about. If you want, you can send the file to me so I can see if this is potentially something Vim did. Otherwise, there's not much to do about this bug report. Vim is behaving as expected when it encounters a malformed viminfo file. You can delete the file so a new one is created or remove that specific line. The viminfo file isn't critical to Vim's functioning. It just stores certain state (command history, buffer history, etc) across Vim runs. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
