68883Re: Bug: Ex command after "motion force" cannot be aborted properly
- Mar 27, 2013Christian,
On Wed, Mar 27, 2013 at 11:01 PM, Christian Brabandt <cblists@...> wrote:
> Ok, what do you think of this updated patch?
Won't there be a redundant call to clearop() now when cancelling
ordinary Ex commands? I suppose it should work though. Thanks.
Personally, I'd rather not patch up bugs where the root cause is
unknown. In this case, the fact remains that "dv:<Esc>" deleted one
character and "dV:<Esc>" deleted one line, and "d:<Esc>" didn't. So I
would prefer to find out how this was possible -- maybe there's more.
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 >>