Re: Problems of new regexp engine (that we know)
Yasuhiro Matsumoto wrote: On Friday, May 24, 2013 2:47:18 AM UTC+9, Bram Moolenaar wrote: Please also write tests. Lots of bugs slipped through because we don't have sufficient testing. https://gist.github.com/mattn/5626661 I added test96 Great, thanks. I fixed all the known problems in the NFA engine. I was looking into making it work faster. However, one syntax that is known to be slow, XML, falls back to the old engine. Thus we need to add the missing features first. Adding the \@= item will be difficult though. I wonder if there is any not-backtracking regexp engine that does something like this. -- I learned the customs and mannerisms of engineers by observing them, much the way Jane Goodall learned about the great apes, but without the hassle of grooming. (Scott Adams - The Dilbert principle) /// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
On Friday, May 24, 2013 2:47:18 AM UTC+9, Bram Moolenaar wrote: Please also write tests. Lots of bugs slipped through because we don't have sufficient testing. https://gist.github.com/mattn/5626661 I added test96 -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Yasuhiro Matsumoto wrote: OK, I'll do it. However I doubt that there are some cases that new regexp engine is slower than original. This change make be possible to work with html file syntax, but re=2 seems to be slower than re=1. The NFA engine is known to be slower on simple patterns, but much faster on complicated patterns. Especially patterns with * or \+ should be faster, because the backtracking engine makes many attempts and retries, while the NFA engine explores all possible solutions in parallel. After tuning and fixing bugs I want to only use the NFA engine for complicated patterns, then we should really see the advantage. The line length also matters. Of course we can't use the NFA engine for items it does not support, thus a mix of * and any not supported item would result in falling back to the (slow) old engine. -- It is too bad that the speed of light hasn't kept pace with the changes in CPU speed and network bandwidth. -- wie...@porcupine.org /// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Bram, I fixed: * \%# * \%23c \%23l * \%23c \%23l * \%23c \%23l * Treat leading * as star character * \_[ * \@! https://gist.github.com/mattn/5626661 Please check this patch. - Yasuhiro Matsumoto -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
As I've said: having vim read plugin/*.vim files and adding some runtimepath/python-lib dir if it exists to sys.dir would be genious. Then people could use plugin/plugin.py only and have it lazily load its code using import Marc Weber -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
On Thursday, May 23, 2013 12:47:20 PM UTC-5, Bram Moolenaar wrote: Friday is the deadline for new features and larger changes. After that it's bug fixing only! Friday in 8 days, I assume, not Friday tomorrow? -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Ben Fritz wrote: On Thursday, May 23, 2013 12:47:20 PM UTC-5, Bram Moolenaar wrote: Friday is the deadline for new features and larger changes. After that it's bug fixing only! Friday in 8 days, I assume, not Friday tomorrow? Yes, end of May. -- Hanson's Treatment of Time: There are never enough hours in a day, but always too many days before Saturday. /// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
OK, I'll do it. However I doubt that there are some cases that new regexp engine is slower than original. This change make be possible to work with html file syntax, but re=2 seems to be slower than re=1. On 5/24/13, Bram Moolenaar b...@moolenaar.net wrote: Yasuhiro Matsumoto wrote: Currently, I'm trying to fix \%# \%23c #%23c . https://gist.github.com/mattn/5626661 I'll send a patch in later. I very much appreciate the help. Please also write tests. Lots of bugs slipped through because we don't have sufficient testing. -- DENNIS: Look, strange women lying on their backs in ponds handing out swords ... that's no basis for a system of government. Supreme executive power derives from a mandate from the masses, not from some farcical aquatic ceremony. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// 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/groups/opt_out. -- - Yasuhiro Matsumoto -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hi, Bram
I found NFA regexp engine bug.
Prerequisite
vim 7.3.1004
set re=0
How to reproduce
vim -N -u NONE -i NONE --noplugin
oEsc
/\n*or /\_.*
Actual
gone infinite loop.
How to take back control. (on linux)
pgrep -lf
kill -9 nnn -- nnn is vim process number checked by pgrep.
I attached patch.
Please check this.
Best regards,
Hirohito Higashi
--
--
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/groups/opt_out.
diff -r 39cff9b39394 src/regexp_nfa.c
--- a/src/regexp_nfa.c Tue May 21 22:38:18 2013 +0200
+++ b/src/regexp_nfa.c Wed May 22 18:04:03 2013 +0900
@@ -2931,8 +2931,10 @@
c = *reginput;
n = 1;
}
- if (c == NUL)
+ if (c == NUL) {
n = 0;
+ reginput_updated = FALSE;
+ }
/* swap lists */
thislist = list[flag];
Re: Problems of new regexp engine (that we know)
Christian Brabandt wrote:
On Di, 21 Mai 2013, Christian Brabandt wrote:
And also not supported yet are \_[...]
collections.
BTW: This patch enables the \_[...] collections.
diff --git a/src/regexp_nfa.c b/src/regexp_nfa.c
--- a/src/regexp_nfa.c
+++ b/src/regexp_nfa.c
@@ -679,9 +679,7 @@
/* \_[ is collection plus newline */
if (c == '[')
- /* TODO: make this work
-* goto collection; */
- return FAIL;
+goto collection;
/* \_x is character class plus newline */
/*FALLTHROUGH*/
@@ -891,7 +889,7 @@
}
break;
-/* collection: */
+collection:
case Magic('['):
/*
* Glue is emitted between several atoms from the [].
That just enables it, doesn't fix the problems caused.
I believe the pattern that failed was \_[0-9]\?\.
Somehow the \_[] eats the line break and then \ fails to match.
Discovered using the dnsmasq syntax, especially the DnsmasqIPv4
match. Using syntax files as a wild test for regexp works quite well.
But it does not find everything (and I still have too few files to test
with).
Here are some more patterns that still fail:
Multi-byte problem? Marc Weber
echo matchlist('1', '\%#=1\o{\?Ä\Z')
echo matchlist('1', '\%#=2\o{\?Ä\Z')
Difference in matching this pattern: (Marc Weber)
echo matchlist(t, '\%#=1ú\Z')
echo matchlist(t, '\%#=2ú\Z')
Difference in matching this pattern:
echo matchlist('google', '\%#=1\go*\|go')
echo matchlist('google', '\%#=2\go*\|go')
Difference in matching this pattern: (Marc Weber)
echo matchlist(\na, '\%#=1\_F')
echo matchlist(\na, '\%#=0\_F')
echo matchlist(\na, '\%#=2\_F')
--
If you don't get everything you want, think of
everything you didn't get and don't want.
/// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hirohito Higashi wrote: Hi, Bram I found NFA regexp engine bug. Prerequisite vim 7.3.1004 set re=0 How to reproduce vim -N -u NONE -i NONE --noplugin oEsc /\n*or /\_.* Actual gone infinite loop. How to take back control. (on linux) pgrep -lf kill -9 nnn -- nnn is vim process number checked by pgrep. I attached patch. Please check this. Great to see a patch for a regexp bug. I'll try it out tonight. It would be nice if we can add a test for every problem we find, so that we make sure it doesn't come back later. -- CART DRIVER: Bring out your dead! There are legs stick out of windows and doors. Two MEN are fighting in the mud - covered from head to foot in it. Another MAN is on his hands in knees shovelling mud into his mouth. We just catch sight of a MAN falling into a well. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hi Bram, I'd be interested in a high level overview about what can/should be done for the release to happen. This way people who are willing to help (eventually me) can pick a task, document that they are working on it, and get it done. Does it exist? If a titanpad or public google documents would be a nice a fit. Thoughts? Marc Weber -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Currently, I'm trying to fix \%# \%23c #%23c . https://gist.github.com/mattn/5626661 I'll send a patch in later. On 5/22/13, Bram Moolenaar b...@moolenaar.net wrote: Hirohito Higashi wrote: Hi, Bram I found NFA regexp engine bug. Prerequisite vim 7.3.1004 set re=0 How to reproduce vim -N -u NONE -i NONE --noplugin oEsc /\n*or /\_.* Actual gone infinite loop. How to take back control. (on linux) pgrep -lf kill -9 nnn -- nnn is vim process number checked by pgrep. I attached patch. Please check this. Great to see a patch for a regexp bug. I'll try it out tonight. It would be nice if we can add a test for every problem we find, so that we make sure it doesn't come back later. -- CART DRIVER: Bring out your dead! There are legs stick out of windows and doors. Two MEN are fighting in the mud - covered from head to foot in it. Another MAN is on his hands in knees shovelling mud into his mouth. We just catch sight of a MAN falling into a well. Monty Python and the Holy Grail PYTHON (MONTY) PICTURES LTD /// 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/groups/opt_out. -- - Yasuhiro Matsumoto -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
One more. \ze does not work. On 5/21/13, Ken Takata ken...@csc.jp wrote: Hi, 2013/05/21 Tue 9:16:55 UTC+9 mattn wrote: * Some plugins doesn't work * \%u is disabled * test64 contains tests for multi-byte * test95 doesn't pass without enc=utf-8 * Strange condition in the line 1094: if (*regparse == 'n' || *regparse == 'n') \%u seems to be disabled because of lack of testing. See the comment in the line 1104. Thanks, Ken Takata -- -- 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/groups/opt_out. -- - Yasuhiro Matsumoto -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Yasuhiro Matsumoto wrote:
* Some plugins doesn't work
Can you please come up with reproducible examples?
* \%u is disabled
You mean it does not work:
echo matchlist('yes no', '\%#=1\%u0020')
echo matchlist('yes no', '\%#=2\%u0020')
However, this does work:
echo matchlist('yes no', '\%#=0\%u0020')
It falls back to the old engine automatically.
So, what is the problem?
* test64 contains tests for multi-byte
Which ones? I suppose you mean that the file contains multi-byte
characters. I can fix that.
* test95 doesn't pass without enc=utf-8
I sent out a patch for that. Please verify it works.
--
Did Adam and Eve have navels?
/// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Ken Takata wrote: 2013/05/21 Tue 9:16:55 UTC+9 mattn wrote: * Some plugins doesn't work * \%u is disabled * test64 contains tests for multi-byte * test95 doesn't pass without enc=utf-8 * Strange condition in the line 1094: if (*regparse == 'n' || *regparse == 'n') Yeah, that's clearly wrong. Now I wonder what it was supposed to be. 'r' perhaps? \%u seems to be disabled because of lack of testing. See the comment in the line 1104. This is only inside a range. Yeah, this function is much too long. So this is about \d, \o, etc. inside []. Not about \%d etc. Look in line 846. -- People who want to share their religious views with you almost never want you to share yours with them. /// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hi Bram! On Di, 21 Mai 2013, Bram Moolenaar wrote: Ken Takata wrote: 2013/05/21 Tue 9:16:55 UTC+9 mattn wrote: * Some plugins doesn't work * \%u is disabled * test64 contains tests for multi-byte * test95 doesn't pass without enc=utf-8 * Strange condition in the line 1094: if (*regparse == 'n' || *regparse == 'n') Yeah, that's clearly wrong. Now I wonder what it was supposed to be. 'r' perhaps? Yes from the context I think so. regards, Christian -- Der sogannte Aberglaube beruht auf einer viel größeren Tiefe und Delikatesse als der Unglaube. -- Johann Wolfgang von Goethe (zu Riemer 12. Dez. 1806) -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hi all, I apologise if this has already been covered elsewhere, but there is so much going on with the new regexp engine that I'm finding it difficult to keep up. I have all patches for 7.3 from 1 to 1000. Setting regexpengine to 2 in my .vimrc on HP-UX and _vimrc on Win64 gives this this message when opening a c source file (say main.c from vim's source): Error detected while processing /trace/tjmt1/vim/73/vim73/runtime/syntax/c.vim: line 154: E475: Invalid argument: cBracket^Itransparent start='\[\|::\@!' end=']\|:' end='}'me=s-1 contains=ALLBUT,cBlock,@cParenGroup,cErrInParen,cCppParen,cCppBracket,cCppString,@Spell line 344: E475: Invalid argument: cCppOutWrapper^Istart="^\s*\(%:\|#\)\s*if\s\+0\+\s*\($\|//\|/\*\|\)" end=".\@=\|$" contains=cCppOutIf,cCppOutElse fold Press ENTER or type command to continue After the file is loaded closing square brackets are highlighted. Opening the syntax file c.vim gives: Error detected while processing /trace/tjmt1/vim/73/vim73/runtime/syntax/vim.vim: line 114: E475: Invalid argument: vimInsert^Imatchgroup=vimCommand start="^[: \t]*\(\d\+\(,\d\+\)\=\)\=a\%[ppend]$"^Imatchgroup=vimCommand end="^\.$"" line 115: E475: Invalid argument: vimInsert^Imatchgroup=vimCommand start="^[: \t]*\(\d\+\(,\d\+\)\=\)\=c\%[hange]$"^Imatchgroup=vimCommand end="^\.$"" line 116: E475: Invalid argument: vimInsert^Imatchgroup=vimCommand start="^[: \t]*\(\d\+\(,\d\+\)\=\)\=i\%[nsert]$"^Imatchgroup=vimCommand end="^\.$"" line 120: E475: Invalid argument: vimBehave^I"\be\%[have]\" skipwhite nextgroup=vimBehaveModel,vimBehaveError line 128: E475: Invalid argument: vimFiletype^I"\filet\%[ype]\(\s\+\I\i*\)*"^Iskipwhite contains=vimFTCmd,vimFTOption,vimFTError line 141: E475: Invalid argument: vimAugroup^Istart="\aug\%[roup]\\s\+\h\w*" end="\aug\%[roup]\\s\+[eE][nN][dD]\"^Icontains=vimAugroupKey,vimAutoCmd,@vimAugroupList keepend a lot of lines removed line 733: E475: Invalid argument: vimEmbedError start=+mz\%[scheme]\s*\s*\z(.*\)$+ end=+^\z1$+ line 749: E475: Invalid argument: vimAugroupSyncA^Igroupthere NONE^I"\aug\%[roup]\\s\+[eE][nN][dD]" Press ENTER or type command to continue Of course this doesn't happen when regexpengine is 1. Cheers John On 21-May-2013 10:16 AM, mattn wrote: * Some plugins doesn't work * \%u is disabled * test64 contains tests for multi-byte * test95 doesn't pass without enc=utf-8 Here is japanese discusstion https://github.com/vim-jp/issues/issues/390#issuecomment-18181263 Thanks. -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hi John! On Mi, 22 Mai 2013, John Marriott wrote: Hi all, I apologise if this has already been covered elsewhere, but there is so much going on with the new regexp engine that I'm finding it difficult to keep up. I have all patches for 7.3 from 1 to 1000. Setting regexpengine to 2 in my .vimrc on HP-UX and _vimrc on Win64 gives this this message when opening a c source file (say main.c from vim's source): Error detected while processing /trace/tjmt1/vim/73/vim73/runtime/syntax/c.vim: line 154: E475: Invalid argument: cBracket^Itransparent start='\[\|::\@!' end=']\|:' \@ assertions are not supported yet by the new engine. line 114: E475: Invalid argument: vimInsert^Imatchgroup=vimCommand start=^[: \t]*\(\d\+\ (,\d\+\)\=\)\=a\%[ppend]$^Imatchgroup=vimCommand end=^\.$ \%[...] is not supported yet by the new engine And also not supported yet are the many \%X atoms and \_[...] collections. I am not sure, if all those need to get fixed before the release. regards, Christian -- Letzte Worte der Mutter: Ich hab mal deine Disketten sortiert. -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
On May 21, 2013 4:06 PM, John Marriott basil...@internode.on.net wrote: I have all patches for 7.3 from 1 to 1000. Setting regexpengine to 2 in my .vimrc [...] Of course this doesn't happen when regexpengine is 1. As I understand it, the default setting is 0 for a reason. The new engine isn't going to handle all the cases the existing engine does. The intention of the default setting is to use the new one where it's better and fallback to the old one when needed, so I don't think you should generally be running with only the new engine active. Cheers, James -- -- 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
John Marriott wrote: html head meta content=text/html; charset=ISO-8859-1 http-equiv=Content-Type /head Can you please send text messages? As mentioned, don't set 'regexpengine' to 2 except for testing. -- THEOREM: VI is perfect. PROOF: VI in roman numerals is 6. The natural numbers 6 which divide 6 are 1, 2, and 3. 1+2+3 = 6. So 6 is a perfect number. Therefore, VI is perfect. QED -- Arthur Tateishi /// 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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
On Di, 21 Mai 2013, Christian Brabandt wrote:
And also not supported yet are \_[...]
collections.
BTW: This patch enables the \_[...] collections.
diff --git a/src/regexp_nfa.c b/src/regexp_nfa.c
--- a/src/regexp_nfa.c
+++ b/src/regexp_nfa.c
@@ -679,9 +679,7 @@
/* \_[ is collection plus newline */
if (c == '[')
- /* TODO: make this work
-* goto collection; */
- return FAIL;
+goto collection;
/* \_x is character class plus newline */
/*FALLTHROUGH*/
@@ -891,7 +889,7 @@
}
break;
-/* collection: */
+collection:
case Magic('['):
/*
* Glue is emitted between several atoms from the [].
regards,
Christian
--
Skepsis ist das Zeichen - und sogar die Pose - des gebildeten
Verstandes.
-- John Dewey
--
--
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/groups/opt_out.
Re: Problems of new regexp engine (that we know)
Hi, 2013/05/21 Tue 9:16:55 UTC+9 mattn wrote: * Some plugins doesn't work * \%u is disabled * test64 contains tests for multi-byte * test95 doesn't pass without enc=utf-8 * Strange condition in the line 1094: if (*regparse == 'n' || *regparse == 'n') \%u seems to be disabled because of lack of testing. See the comment in the line 1104. Thanks, Ken Takata -- -- 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/groups/opt_out.
