Re: Problems of new regexp engine (that we know)

2013-05-27 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-26 Fir de Conversatie mattn
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!

Re: Problems of new regexp engine (that we know)

2013-05-24 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-23 Fir de Conversatie mattn
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

Re: Problems of new regexp engine (that we know)

2013-05-23 Fir de Conversatie Marc Weber
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.

Re: Problems of new regexp engine (that we know)

2013-05-23 Fir de Conversatie Ben Fritz
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

Re: Problems of new regexp engine (that we know)

2013-05-23 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-23 Fir de Conversatie Yasuhiro MATSUMOTO
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:

Re: Problems of new regexp engine (that we know)

2013-05-22 Fir de Conversatie h_east
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.

Re: Problems of new regexp engine (that we know)

2013-05-22 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-22 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-22 Fir de Conversatie Marc Weber
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

Re: Problems of new regexp engine (that we know)

2013-05-22 Fir de Conversatie Yasuhiro MATSUMOTO
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Yasuhiro MATSUMOTO
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Christian Brabandt
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie John Marriott
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Christian Brabandt
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie James McCoy
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Bram Moolenaar
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

Re: Problems of new regexp engine (that we know)

2013-05-21 Fir de Conversatie Christian Brabandt
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

Re: Problems of new regexp engine (that we know)

2013-05-20 Fir de Conversatie Ken Takata
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