Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 134 by hkpt...@gmail.com: Pasting over visually selected line of
new buffer not correctly undoable
http://code.google.com/p/vim/issues/detail?id=134
Steps to reproduce:
1. vim -u NONE -N
2. ifooyy
3. :ene!
4. Vp
5. u
6. :se
On 21 May 2013, Ben Fritz wrote:
> On Tuesday, May 21, 2013 9:13:37 PM UTC-5, toothpik wrote:
> > my issue with slow scrolling in index.html with cursorline turned on
> >
> > goes away when I set regexpengine=1
> >
> >
> >
> > huge GTK2 7.3.1004 with python 2.7
>
> IIUC, cursorline causes a s
On 21 May 2013, Christian Brabandt wrote:
[...]
> getlocstack() returns the location list stack as list
> getlocstackptr() returns the current position in the location list stack
> getloctitle() returns a list of titles for the location list stack
> getqfstack() returns the q
On Tuesday, May 21, 2013 9:13:37 PM UTC-5, toothpik wrote:
> my issue with slow scrolling in index.html with cursorline turned on
>
> goes away when I set regexpengine=1
>
>
>
> huge GTK2 7.3.1004 with python 2.7
IIUC, cursorline causes a slow-down even with the old regex engine because it
fo
I'm trying to contact Sureshkumar Manimuthu, who authored the vimgdb tool. The
email address he gave there seems to be inactive now.
Does anyone have contact information for him?
Thanks!
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the t
my issue with slow scrolling in index.html with cursorline turned on
goes away when I set regexpengine=1
huge GTK2 7.3.1004 with python 2.7
--
--
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, vis
Using 7.3.1004 on Win 7 64 bit.
gvim -u NONE -U NONE --noplugins
:set re=0
:echo split(" TBD NOTE XXX FIXME TODO \n")
['TBD', 'NOTE', 'XXX', 'FIXME', 'TODO', '
']
:set re=1
:echo split(" TBD NOTE XXX FIXME TODO \n")
['TBD', 'NOTE', 'XXX', 'FIXME', 'TODO']
This is a distilled case, it is affecti
On 05/21/2013 10:38 PM, Bram Moolenaar wrote:
Patch 7.3.1004
Problem:No error when option could not be set.
Solution: Report an error. (ZyX)
Files: src/if_py_both.h, src/option.c, src/proto/option.pro,
src/testdir/test86.ok, src/testdir/test87.ok
*** ../vim-7.3.1003/src/
>
> > Was this patch applied already?
>
> >
>
> > I tried compiling a 64 bit windows but if failed complaining that some
>
> > include file could not be found.
>
> >
>
> > If possible could this patch be included for the next release?
>
>
>
> AFAIK this was included in patch 7.3.889.
>
On 21 May 2013, Christian Brabandt wrote:
>
> On Mi, 22 Mai 2013, LCD 47 wrote:
>
> > I see. Can you please post that as a single patch, against a
> > well-defined version of Vim? There are several versions floating around
> > by now, and figguring out which pieces are still current and wh
On Tuesday, May 21, 2013 3:01:05 PM UTC-5, Bram Moolenaar wrote:
> Skeept wrote:
>
>
>
> > > Thanks. I hope a few people can try it out.
>
> >
>
> > Was this patch applied already?
>
> >
>
> > I tried compiling a 64 bit windows but if failed complaining that some
>
> > include file coul
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 c
On Mi, 22 Mai 2013, LCD 47 wrote:
> I see. Can you please post that as a single patch, against a
> well-defined version of Vim? There are several versions floating around
> by now, and figguring out which pieces are still current and which are
> obsolete is, well, too complex a task for my
On 21 May 2013, Christian Brabandt wrote:
> Hi vim-dev!
>
> On Di, 21 Mai 2013, Christian Brabandt wrote:
>
> > Hi LCD!
> >
> > On Di, 21 Mai 2013, LCD 47 wrote:
> >
> > > On 21 May 2013, Christian Brabandt wrote:
> > > [...]
> > > > Attached is an updated patch. It adds the following functio
Hi Bram!
On Di, 21 Mai 2013, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Di, 21 Mai 2013, Bram Moolenaar wrote:
> >
> > > It's the new regexp engine. If this bothers you set 'regexpengine' to
> > > 1. It's not the default because we want to fix the slowness.
> > > Patch 7.3.
John Marriott wrote:
>
>
>http-equiv="Content-Type">
>
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+
Christian Brabandt wrote:
> On Di, 21 Mai 2013, Bram Moolenaar wrote:
>
> > It's the new regexp engine. If this bothers you set 'regexpengine' to
> > 1. It's not the default because we want to fix the slowness.
> > Patch 7.3.988 should help.
>
> Globbing is still (7.3.996) very slow, even wit
Patch 7.3.1004
Problem:No error when option could not be set.
Solution: Report an error. (ZyX)
Files: src/if_py_both.h, src/option.c, src/proto/option.pro,
src/testdir/test86.ok, src/testdir/test87.ok
*** ../vim-7.3.1003/src/if_py_both.h2013-05-21 22:23:50.0 +0
Hi vim-dev!
On Di, 21 Mai 2013, Christian Brabandt wrote:
> Hi LCD!
>
> On Di, 21 Mai 2013, LCD 47 wrote:
>
> > On 21 May 2013, Christian Brabandt wrote:
> > [...]
> > > Attached is an updated patch. It adds the following functions:
> > >
> > > getlocstack() returns the location list st
Hi Matthew!
On Di, 21 Mai 2013, Matthew Winn wrote:
> On Tue, 21 May 2013 09:51:37 -0700 (PDT), Kirill Serkh
> wrote:
>
> > In 2007 Matthew Winn published a patch against vim 7.1.135 for non-uniform
> > tabstops (i.e. setting tabstops at user-defined columns) [1]. It was voted
> > on in 2008
> Patch 7.3.1003
> Problem:Python interface does not compile with Python 2.2
> Solution: Fix thread issues and True/False. (ZyX)
?! I did not fix threading issues and True/False. I just said that after these
fixes it compiles with python-2.2, but tests *fail* due to threading and
True/Fals
On May 21, 2013 4:06 PM, "John Marriott" 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
Patch 7.3.1003
Problem:Python interface does not compile with Python 2.2
Solution: Fix thread issues and True/False. (ZyX)
Files: src/if_py_both.h, src/if_python3.c, src/if_python.c,
src/testdir/test86.in, src/testdir/test86.ok,
src/testdir/test87.in, src/testdir
What the...
Bram is on a spree, eh? :-)
--
--
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
On Tue, 21 May 2013 09:51:37 -0700 (PDT), Kirill Serkh
wrote:
> In 2007 Matthew Winn published a patch against vim 7.1.135 for non-uniform
> tabstops (i.e. setting tabstops at user-defined columns) [1]. It was voted on
> in 2008 [2] but never made its way into vim (?).
[snip]
> I'm trying to fi
Patch 7.3.1002
Problem:Valgrind errors for Python interface.
Solution: Fix memory leaks when running tests. (ZyX)
Files: src/if_py_both.h
*** ../vim-7.3.1001/src/if_py_both.h2013-05-21 20:51:55.0 +0200
--- src/if_py_both.h2013-05-21 22:08:25.0 +0200
***
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 i
Hi LCD!
On Di, 21 Mai 2013, LCD 47 wrote:
> On 21 May 2013, Christian Brabandt wrote:
> [...]
> > Attached is an updated patch. It adds the following functions:
> >
> > getlocstack() returns the location list stack as list
> > getlocstackptr() returns the current position in the locati
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 Di, 21 Mai 2013, Bram Moolenaar wrote:
> It's the new regexp engine. If this bothers you set 'regexpengine' to
> 1. It's not the default because we want to fix the slowness.
> Patch 7.3.988 should help.
Globbing is still (7.3.996) very slow, even with patterns, that should
work well for th
Skeept wrote:
> > Thanks. I hope a few people can try it out.
>
> Was this patch applied already?
>
> I tried compiling a 64 bit windows but if failed complaining that some
> include file could not be found.
>
> If possible could this patch be included for the next release?
AFAIK this was i
Patch 7.3.1001
Problem:Duplicate condition in if.
Solution: Remove one condition.
Files: src/regexp_nfa.c
*** ../vim-7.3.1000/src/regexp_nfa.c2013-05-21 21:20:16.0 +0200
--- src/regexp_nfa.c2013-05-21 21:56:45.0 +0200
***
*** 1091,1097
On 21 May 2013, Christian Brabandt wrote:
[...]
> Attached is an updated patch. It adds the following functions:
>
> getlocstack() returns the location list stack as list
> getlocstackptr() returns the current position in the location list stack
> getloctitle() returns a list of ti
I wrote:
> Patch 7.3.1000 (whoa!)
Well, there you have it. More than 999 patches.
1000 does not sort below 999, thus this might cause problems perhaps.
I had to fix my script that uploads to ftp.vim.org, for example.
I still think it's better to continue this way than to create some early
7.4
>
>
>
> Thanks. I hope a few people can try it out.
>
>
Was this patch applied already?
I tried compiling a 64 bit windows but if failed complaining that some include
file could not be found.
If possible could this patch be included for the next release?
A small example on how to use rub
Patch 7.3.1000 (whoa!)
Problem:Typo in char value causes out of bounds access.
Solution: Fix character value. (Klemens Baum)
Files: src/regexp.c
*** ../vim-7.3.999/src/regexp.c 2013-05-21 00:02:54.0 +0200
--- src/regexp.c2013-05-21 21:25:58.0 +0200
***
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 condit
Klemens Baum wrote:
> wget -O /tmp/test http://vpaste.net/xCht6?raw && vi /tmp/test
>
> Patch: http://vpaste.net/teceG
A bit more text would have been useful. Anyway, I get the idea from the
patch itself. Must have been there for a while.
--
SOLDIER: What? Ridden on a horse?
ARTHUR: Yes!
S
Patch 7.3.999
Problem:New regexp engine sets curbuf temporarily.
Solution: Use reg_buf instead, like the old engine.
Files: src/regexp_nfa.c
*** ../vim-7.3.998/src/regexp_nfa.c 2013-05-21 16:28:05.0 +0200
--- src/regexp_nfa.c2013-05-21 21:15:41.0 +0200
On Saturday, May 18, 2013 7:15:27 AM UTC-4, Xavier de Gaye wrote:
> runtime/doc/tags is under Mercurial control:
>
> $ hg locate runtime/doc/tags
> runtime/doc/tags
>
> This file is automatically generated during vim build.
> It is annoying to have it appear sometimes in the output of 'hg
In 2007 Matthew Winn published a patch against vim 7.1.135 for non-uniform
tabstops (i.e. setting tabstops at user-defined columns) [1]. It was voted on
in 2008 [2] but never made its way into vim (?).
This feature is very important for editing Fortran and is sorely missed. I
believe it was #10
wget -O /tmp/test http://vpaste.net/xCht6?raw && vi /tmp/test
Patch: http://vpaste.net/teceG
--
--
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 re
Dominique Pelle wrote:
> > > Attached patch fixes a memory leak in regexp_nfa.c
> > > detected by valgrind:
> > >
> > > ==3055== 128 bytes in 4 blocks are definitely lost in loss record 76 of
> > > 110
> > > ==3055==at 0x4C2B3F8: malloc (in
> > > /usr/lib/valgrind/vgpreload_memcheck-amd64-li
Patch 7.3.998
Problem:Python: garbage collection issues.
Solution: Fix the GC issues: Use proper DESTRUCTOR_FINISH: avoids negative
refcounts, use PyObject_GC_* for objects with tp_traverse and
tp_clear, add RangeTraverse and RangeClear, use Py_XDECREF in some
Patch 7.3.997
Problem:Vim and Python exceptions are different.
Solution: Make Vim exceptions be Python exceptions. (ZyX)
Files: src/if_py_both.h, src/testdir/test86.in, src/testdir/test86.ok,
src/testdir/test87.in, src/testdir/test87.ok
*** ../vim-7.3.996/src/if_py_both.h
On Do, 16 Mai 2013, LCD 47 wrote:
> On 15 May 2013, Christian Brabandt wrote:
> > Hi LCD!
> >
> > On Mi, 15 Mai 2013, LCD 47 wrote:
> >
> > > (1) getqfstack() / getlocstack() should simply return a list of
> > > loclists;
> > > (2) there should be a separate function for getting (and perha
Patch 7.3.996
Problem:Python: Can't check types of what is returned by bindeval().
Solution: Add vim.List, vim.Dictionary and vim.Function types. (ZyX)
Files: runtime/doc/if_pyth.txt, src/if_py_both.h, src/testdir/test86.in,
src/testdir/test86.ok, src/testdir/test87.in,
Bram Moolenaar wrote:
>
> Dominique Pelle wrote:
>
> > Attached patch fixes a memory leak in regexp_nfa.c
> > detected by valgrind:
> >
> > ==3055== 128 bytes in 4 blocks are definitely lost in loss record 76 of 110
> > ==3055==at 0x4C2B3F8: malloc (in
> > /usr/lib/valgrind/vgpreload_memcheck
Patch 7.3.995
Problem:Python: Module initialization is duplicated.
Solution: Move to shared file. (ZyX)
Files: src/if_py_both.h, src/if_python3.c, src/if_python.c
*** ../vim-7.3.994/src/if_py_both.h 2013-05-21 19:01:51.0 +0200
--- src/if_py_both.h2013-05-21 19:07:17.00
Patch 7.3.994
Problem:Python: using magic constants.
Solution: Use descriptive values for ml_flags. (ZyX)
Files: src/if_py_both.h, src/if_python3.c
*** ../vim-7.3.993/src/if_py_both.h 2013-05-21 18:47:17.0 +0200
--- src/if_py_both.h2013-05-21 18:51:12.0 +0200
*
Patch 7.3.993
Problem:Python: Later patch does things slightly differently.
Solution: Adjusted argument type changes. (ZyX)
Files: src/if_py_both.h, src/if_python3.c, src/if_python.c
*** ../vim-7.3.992/src/if_py_both.h 2013-05-21 18:30:29.0 +0200
--- src/if_py_both.h20
Patch 7.3.991
Problem:More can be shared by Python 2 and 3.
Solution: Move more stuff to if_py_both. (ZyX)
Files: src/if_py_both.h, src/if_python3.c, src/if_python.c,
src/testdir/test87.ok
*** ../vim-7.3.990/src/if_py_both.h 2013-05-17 21:20:13.0 +0200
--- src/
> retry with syn off or filetype off.
with syntax off the problem seems to be drastically reduced, but not
disappeared completely. however i verified this just with my eyes, no profiling
at all. i just see a small delay loading the last file while the first few
where loaded instantly. anyway, i
Yasuhiro Matsumoto wrote:
> Thanks. BTW) I was thinking that vim's regexp engine can't handle CJK
> class names like [[::katakana::]] and it's nessecary for CJK people.
> Some regexp engine support CJK class names.
> How about to add this?
Let's fix bugs before adding new features. There are to
Marc Weber wrote:
> Yet another suggestion - what about adding &rtp to sys.path somehow ?
> (with or without python version site-packages or the like)
>
> Then you could
> - write .py files
> - use them from python by
>
> import module
> do_stuff()
>
> Yes - it can be trivially impleme
Yasuhiro Matsumoto wrote:
> One more. \ze does not work.
I disabled that, because it's flawed in the new engine, so the automatic
selection should use the old engine, right?
--
Mushrooms always grow in damp places and so they look like umbrellas.
/// Bram Moolenaar -- b...@moolenaar.net -- h
Thanks Bram. That worked like a charm.
On 5/21/2013 9:55 AM, Bram Moolenaar wrote:
> Jeff wrote:
>
>> I just updated Vim with the latest patches (attached is a screenshot of
>> my configuration and version information) and it seems very slow when
>> attempting to use the h,j,k, and l keys. When
retry with syn off or filetype off.
Do your problems still occur?
Excerpts from Matteo Cavalle> "foo2.tpl" 36L, 1231C
> smarty
> smarty
> smarty
> Press ENTER or type command to continue
YOu may want to start vim -V20/tmp/log
then have a look for echo echom echoe lines outputting smarty.
It loo
On Tuesday, May 21, 2013 9:27:34 AM UTC-5, Bram Moolenaar wrote:
> Dominique Pelle wrote:
>
>
>
> > Attached patch fixes a memory leak in regexp_nfa.c
>
> > detected by valgrind:
>
> >
>
> > ==3055== 128 bytes in 4 blocks are definitely lost in loss record 76 of 110
>
> > ==3055==at 0x4
Patch 7.3.990
Problem:Memory leak in new regexp engine.
Solution: Jump to end of function to free memory. (Dominique Pelle)
Files: src/regexp_nfa.c
*** ../vim-7.3.989/src/regexp_nfa.c 2013-05-21 15:33:37.0 +0200
--- src/regexp_nfa.c2013-05-21 16:17:15.0 +0200
*
Dominique Pelle wrote:
> Attached patch fixes a memory leak in regexp_nfa.c
> detected by valgrind:
>
> ==3055== 128 bytes in 4 blocks are definitely lost in loss record 76 of 110
> ==3055==at 0x4C2B3F8: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==3055==by 0x50E
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
>
> Did you measure this before patch 988?
>
> Patch 989 may also help a little bit.
Just rechecked with all patches through 989, the results are similar (this on
32-bit; the other was 64-bit)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply belo
Marc Weber wrote:
> > I fixed \F yesterday. Hmm, but you say you include patch 981.
> > What is the Vim command to reproduce this?
> [1]
>
> > > let reg = 'ú\Z'
> > > let t = ""
> > > echo matchlist('\%#=1'.reg, t)
> > > echo matchlist('\%#=2'.reg, t)
> > Isn't this the same for the ol
Karsten Hopp wrote:
> Am 19.05.2013 19:15, schrieb Bram Moolenaar:
> > Patch 7.3.970
> > Problem:Syntax highlighting can be slow.
> > Solution: Include the NFA regexp engine. Add the 'regexpengine' option to
> > select which one is used. (various authors, including Ken Takata,
> >
Ron Aaron wrote:
> Timing using:
>
> time gvim -f --cmd 'set re=1' -c ':qa!'
>
> 0.285s
>
> with 're=2' or 're=0'
>
> 0.494s
Did you measure this before patch 988?
Patch 989 may also help a little bit.
Problem with the new engine is that the overhead for simple things is
big. It really onl
Jeff wrote:
> I just updated Vim with the latest patches (attached is a screenshot of
> my configuration and version information) and it seems very slow when
> attempting to use the h,j,k, and l keys. When I press the h,j,k, or l
> key, Vim's CPU utilization ramps up to 25%.
>
> I tracked it do
Patch 7.3.989
Problem:New regexp engine compares negative numbers to character.
Solution: Add missing case statements.
Files: src/regexp_nfa.c
*** ../vim-7.3.988/src/regexp_nfa.c 2013-05-21 14:02:55.0 +0200
--- src/regexp_nfa.c2013-05-21 15:31:47.0 +0200
**
> I fixed \F yesterday. Hmm, but you say you include patch 981.
> What is the Vim command to reproduce this?
[1]
> > let reg = 'ú\Z'
> > let t = ""
> > echo matchlist('\%#=1'.reg, t)
> > echo matchlist('\%#=2'.reg, t)
> Isn't this the same for the old and the new engine?
right, I can no
i've tried to do some experimentations... here's what i found. If i run vim and
give the command
:au Syntax * echo expand("")
the first time i load a file i get
"foo1.tpl" 36L, 1231C
smarty
Press ENTER or type command to continue
then i load another file and get
"foo2.tpl" 36L, 1231C
sma
Hi
Attached patch fixes a memory leak in regexp_nfa.c
detected by valgrind:
==3055== 128 bytes in 4 blocks are definitely lost in loss record 76 of 110
==3055==at 0x4C2B3F8: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3055==by 0x50E98C: lalloc (misc2.c:929)
==3055==
sometimes vim takes a lot of time to load a file, and the more file i load, the
more time it takes (i'm talking about even 20 seconds or more).
i've been able to reproduce the problem by just loading 10 identical files one
after the other. it seems a problem with my configuration, as using "vim
Am 19.05.2013 19:15, schrieb Bram Moolenaar:
Patch 7.3.970
Problem:Syntax highlighting can be slow.
Solution: Include the NFA regexp engine. Add the 'regexpengine' option to
select which one is used. (various authors, including Ken Takata,
Andrei Aiordachioaie, Russ
Timing using:
time gvim -f --cmd 'set re=1' -c ':qa!'
0.285s
with 're=2' or 're=0'
0.494s
--
--
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 re
Patch 7.3.988
Problem:New regexp engine is slow.
Solution: Break out of the loop when the state list is empty.
Files: src/regexp_nfa.c
*** ../vim-7.3.987/src/regexp_nfa.c 2013-05-21 12:43:52.0 +0200
--- src/regexp_nfa.c2013-05-21 14:01:33.0 +0200
**
Patch 7.3.987
Problem:No easy to run an individual test. Tests 64 fails when
'encoding' is not utf-8.
Solution: Add individual test targets to the Makefile. Move some lines from
test 64 to 95.
Files: src/Makefile, src/testdir/test64.in, src/testdir/test64.ok,
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
Patch 7.3.986
Problem:Test 95 doesn't pass when 'encoding' isn't utf-8. (Yasuhiro
Matsumoto)
Solution: Force 'encoding' to be utf-8.
Files: src/testdir/test95.in
*** ../vim-7.3.985/src/testdir/test95.in2013-05-21 12:34:13.0
+0200
--- src/testdir/test95.in
Ron Aaron wrote:
> I know it's late to vote, but some sort of sane 'gdb' integration would
> be supremely useful. I haven't found any packages for this that don't
> involve a lot of setup.
There are several implementations, including my own "Agide".
Pick one that is the best and improve it...
M
> you need to do "syn clear", because the compiled pattern
I tested this after restarting vim each times.
--
--
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
Patch 7.3.985
Problem:GTK vim not started as gvim doesn't set WM_CLASS property to a
useful value.
Solution: Call g_set_prgname() on startup. (James McCoy)
Files: src/gui_gtk_x11.c
*** ../vim-7.3.984/src/gui_gtk_x11.c2013-05-06 04:21:35.0 +0200
--- src/gui_gtk_
On Tuesday, May 21, 2013 7:44:10 PM UTC+9, Bram Moolenaar wrote:
> Yasuhiro Matsumoto wrote:
>
>
>
> > On Tuesday, May 21, 2013 7:04:55 PM UTC+9, Bram Moolenaar wrote:
>
> >
>
> > Some syntax hilighighting won't work even though re=1.
>
> > For example:
>
> >
>
> > 1. type "google"
>
> >
Patch 7.3.984
Problem:A Visual mapping that uses CTRL-G works differently when started
from Insert mode. (Ein Brown)
Solution: Reset old_mapped_len when handling typed text in Select mode.
Files: src/normal.c
*** ../vim-7.3.983/src/normal.c 2013-05-06 04:21:35.0 +0
Yasuhiro Matsumoto wrote:
> On Tuesday, May 21, 2013 7:04:55 PM UTC+9, Bram Moolenaar wrote:
>
> Some syntax hilighighting won't work even though re=1.
> For example:
>
> 1. type "google"
> 2. :syn clear | syn match ErrorMsg "\
> Using vim that older than 970:
>
> http://go-gyazo.appspot.com/
Patch 7.3.983
Problem:Uneccessary temp variable.
Solution: Remove the variable.
Files: src/regexp_nfa.c
*** ../vim-7.3.982/src/regexp_nfa.c 2013-05-21 12:34:13.0 +0200
--- src/regexp_nfa.c2013-05-21 12:35:37.0 +0200
***
*** 2833,2839
int
Patch 7.3.982
Problem:In the new regexp engine \p does not work on multi-byte
characters.
Solution: Don't point to an integer but the characters.
Files: src/regexp_nfa.c, src/testdir/test95.in, src/testdir/test95.ok
*** ../vim-7.3.981/src/regexp_nfa.c 2013-05-20 22:19:
On Tuesday, May 21, 2013 7:04:55 PM UTC+9, Bram Moolenaar wrote:
Some syntax hilighighting won't work even though re=1.
For example:
1. type "google"
2. :syn clear | syn match ErrorMsg "\http://go-gyazo.appspot.com/a16424e8636121c6.png
Using vim that 970 or later:
http://go-gyazo.appspot.com/42
Cesar Romani wrote:
> By updating from 7.3.969 to 7.3.981 the following command doesn't work
> anymore:
> %s/""/\='"'.matchstr(getline("."), '\d\+\ze<').'"'
>
> Let's say I use this command on the following text:
> Table of Contents 5
> Acknowledgements 7
> Preface 9
> Introduction to the Second
Marc Weber wrote:
> 1) That the new regex *silently* fails if something is not supported is
> no option - you should throw an error IMHO so that people know that
> something goes wrong.
It happens if you set 'regexpengine' to 2.
> 2) https://gist.github.com/MarcWeber/5616733
> I've created
One more. \ze does not work.
On 5/21/13, Ken Takata 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
90 matches
Mail list logo