2

As I'm using Neovim, I'm noticing my marks are just disappearing mid session. I keep having to define them over and over again. I swear it's got to be a bug, either in Neovim or a plugin I'm using, but I'm curious if there's any possible way to debug this—something along the lines of verbose perhaps. This is getting really annoying.

Mason
  • 521
  • 4
  • 15
  • I would say that the first thing to check is How to debug your vimrc because that's the most probable source of issues. Also -just to make sure it's not something obvious- is it not due to a misunderstanding of the difference between buffer local marks ma and global marks mA? – statox Jan 31 '20 at 09:08
  • @statox I'm using buffer local marks, but I'm not reloading my client or unloading the buffer (at least I don't think I am, I don't even know how to unload a buffer) – Mason Jan 31 '20 at 09:23
  • Then try to replicate the problem without a vimrc and if you can't replicate without it, the question I linked should be useful. You could also tell us the details of the neovim version you are using. – statox Jan 31 '20 at 09:51
  • @statox my config is pretty minimal and I really don't wanna go without the plugins I have, so I guess I'm SOL. – Mason Feb 01 '20 at 20:15

1 Answers1

2

As far as I'm aware, Vim does not include any features that will help you track down what's causing this issue, so you have two options, neither of which are very appealing.

  1. You can follow statox's advice, and attempt to narrow down what part of your configuration is causing the issue by selectively disabling parts of your vimrc and disabling/removing your plugins systematically. This is a pain for this sort of issue because the fact that it just occurs randomly after a period of time means that it's going to take you ages to track down the problem, and while you are doing so you'll be missing parts of your Vim environment making using it more difficult. Unpleasant.

  2. You can download the Vim source code, set up a dev environment, learn how to debug C code (if you don't already know how to do so) figure out which bits of the Vim source code are run when a mark is removed/reset, set breakpoints on these, and then carry out your normal tasks until the breakpoint is hit. If you're not already a C programmer, this is not really feasible, and even if you are, it's a big task.

Sorry!

Rich
  • 31,891
  • 3
  • 72
  • 139
  • yikers {char limit} – Mason Feb 01 '20 at 20:12
  • You could also track changes in the info file, where the markers are saved . Possibly some of it gets updated in real-time. – eyal karni Feb 03 '20 at 01:51
  • You can also work with vim profiling to figure out what is wrong. – eyal karni Feb 03 '20 at 01:51
  • 2
    @eyalkarni Interesting ideas! The viminfo file isn't updated in real time, but you can initiate a write with the :wviminfo command, so you could set that up on a timer to get a rough idea of when the marks are being deleted. I'm not sure how you could use profiling to help debug this problem, but I'd be interested to hear your ideas. You should write an answer! – Rich Feb 03 '20 at 09:34