I don't think that additional threads are going to help
There is an issue, and we should find a way to fix (IMHO).
Let me summarize again - and tell me if you feel differently.
Test cases:
[1] echo len(matchstr("\n",'\zs[^\n]\ze'))
[2] echo len(matchstr("\n","\\zs[^\n]\\ze"))
I expect both do the same, the difference is that the second as chr(10) in [^],
while the first has \n (which should be translated to chr(10).
However I obsorve that [2] returns 0 as expected , but [1] does return
1, thus it matches \n even though I told Vim that I do not want to match
it. People told me this was because '.' is equal to [^\n].
Current situation: at least to be fixed
1:
No matter whether '.' should behave like [^\n]
[1] and [2] should behave the same, right?
2:
This should be documented.
(Do you all at least agree these two statments?)
If so which is the best way to fix this - and which should be the way to
express [^\n] meaning do not match \n rather than behave like '.' then ?
Marc Weber
--
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
