On 10:15 Wed 31 Oct , Ingo Karkat wrote:
> On 31-Oct-2012 10:02:33 +0100, Marcin Szamotulski wrote:
>
> > Dear Vim Dev,
> >
> > I recently found that v with count remembers the previous visual area.
> > I found that it is not always true, which seems strange to me (is this
> > a feature or a bug?). For example if I do "v{motion}y", then "1v", as
> > should, selects the same are in the current position. But if I do
> > "v{motion}<esc>" or "v{motion}<c-c>" then "1v" doesn't remember the
> > last visual area but the previous one. With <esc>/<c-c> I thing it
> > would be nice if <esc> could remember the last area and <c-c> don't
> > (this already happens with some features: for example <c-c> doesn't
> > trigger InsertLeave autocommands when leaving the insert mode.)
>
> This has been discussed before:
>
> https://groups.google.com/d/topic/vim_dev/381bdn3wuuM/discussion
>
> >From Bram:
> > > The idea of "1v" is that a Visual operation can be repeated at another
> > > location. Thus the area is only stored when performing an operation.
>
> Like you, some found this behavior unexpected, but we couldn't convince Bram
> to
> change this (mostly to avoid breaking stuff that potentially relies on this
> behavior), and no patches were put forward.
>
> -- regards, ingo
>
> --
> 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
Good to know.
Is there a VimL workaround, or a plugin for this?
Best,
Marcin
--
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
