On 17.02.13 14:03, Marc Weber wrote:
> This doesn't make sense. If I ask to not match \n I don't want \n to be
> matched. Its about following the principle of least surprise.
+1
> The burden to learn vim specific regex is already high enough for most
> users.
And too much for some. The failure to employ posix EREs is Vim's only
true failing, IME. (OK, by prefixing \v to every regex, we get
reasonably close.)
...
> Vim should also follow the principle of "least suprprise" - and [^\n] is
> supposed to not match \n.
>
> There is more future than past - so its ok to break compatiblity in such
> an obvious case IMHO.
It is a compelling case - ya gotta admit.
Erik
--
Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
- A. P. J.
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sunday, February 17, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment