68885Re: Bug: Ex command after "motion force" cannot be aborted properly
- Mar 28, 2013Christian,
On Wed, Mar 27, 2013 at 11:01 PM, Christian Brabandt <cblists@...> wrote:
> Ok, what do you think of this updated patch?
You are of course correct.
I now see that a motion given with an Ex command is exclusive by
default, and "v" and "V" toggle inclusive/exclusive, and that is why
eventually the character or the line under the cursor are deleted.
I think your solution is fine, thanks a lot. I have attached a patch
that avoids calling clearop() when it isn't necessary and avoids calling
both clearop() and clearopbeep(), it's just a little bit more verbose.
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 vim_dev+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
- << Previous post in topic Next post in topic >>