On Saturday, May 23, 2015 at 10:52:16 PM UTC+2, Justin M. Keyes wrote:
> But why can't keepjumps be made recursive instead?
That's the first thing I thought too. Of course it would break existing code,
so it should be something else, perhaps keepjumps!. But it also seemed a more
complicated and less flexible model to me: does it apply to exec'd code,
mappings etc.? Well, essentially if the answer to all questions is no you'd
almost have what I have here. One trickier point is what to do if the code
changes window.
The option route seemed the most straightforward to me; I can have a look at a
different implementation (but again, my knowledge of vim source code is
extremely poor).
> These one-off commands ("keepjumps", "lockjumps", etc, etc) are
> extremely disappointing to me. Why can't there be, instead, a general
> mechanism to save/restore these lists? Similar to
> winsaveview()/winrestview(), except, you know--not a band-aid
> solution. A *general* solution.
I'm open to suggestions, but I don't see what you have in mind exactly. Care to
elaborate?
--
--
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].
For more options, visit https://groups.google.com/d/optout.
