|
I've silently, and gladly, used your plugin for well over a decade now, and it's been absolutely magical--especially when viewing telemetry / log files that log tracing info (i.e. function calls/returns and variables) with the same names as in code. Highlight them in the log, see them light up in code, and vice versa. And being able to use vim-native patterns ( Q: Is there a convenient way to save marks as part of the I use vim sessions when, eg, treesitter causes P.S. Here's a new contender for your Related Works section: high-str |
Replies: 1 comment 3 replies
|
I so far thought that having global mark persistence in the Fortunately, the mechanism used for mark persistence in I've implemented that in mark.vim version 3.4.0; you also need to update the ingo-library dependency (to 1.047, as neither Vim nor Neovim support List variables in session files yet; I've opened an issue for that). |
[marking this as the answer because it has both of your answers collected in one config]
Thanks, that did the trick. For future searchers, my config is now: