Loading ...
Sorry, an error occurred while loading the content.

Re: Bug: Ex command after "motion force" cannot be aborted properly

Expand Messages
  • glts
    Sorry for being spammy: ... Nonsense. The patch avoids a) calling clearop() when it isn t necessary and b) *not beeping* when did_emsg == TRUE and cmd_result
    Message 1 of 9 , Mar 28, 2013
    • 0 Attachment
      Sorry for being spammy:

      On Thu, Mar 28, 2013 at 1:16 PM, glts <676c7473@...> wrote:
      > On Wed, Mar 27, 2013 at 11:01 PM, Christian Brabandt <cblists@...> wrote:
      >> Ok, what do you think of this updated patch?
      >
      > 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.

      Nonsense. The patch avoids
      a) calling clearop() when it isn't necessary and
      b) *not beeping* when did_emsg == TRUE and cmd_result == FAIL

      --
      --
      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.
    Your message has been successfully submitted and would be delivered to recipients shortly.