Andy Wokula wrote: > Am 13.05.2018 um 18:36 schrieb Bram Moolenaar: > > Patch 8.0.1837 > > Problem: One character cmdline abbreviation not triggered after '<,'>. > > Solution: Skip over the special range. (Christian Brabandt, closes #2320) > > Files: src/ex_getln.c, src/testdir/test_mapping.vim > > Do you have a good feeling when adding such inconsistencies? > I'd rather keep such a "bug".
In Insert mode the abbreviation also triggers when it's at the point where the current insert started. This is similar: pressing a key when Visual mode is active. Thus it's the first character typed in the command line. We could extend it to skip the range, but parsing a range isn't that easy. Let's see if someone runs into this problem. -- Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke Any sufficiently advanced bug is indistinguishable from a feature. Rich Kulawiec /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.