Re: Patch 7.4.1926

2016-06-15 Fir de Conversatie Christian Brabandt
Am 2016-06-15 23:05, schrieb Bram Moolenaar: Christian Brabandt wrote: > Have you tried after patch 7.4.1939? It fixes a problem where > w_jumplistlen was overwritten with a line number. Valgrind doesn't > catch this because it's still within a struct. I saw that patch, and it looks suspicio

Re: [vim/vim] Automatic regular expression engine selection matches incorrectly on long line (#867)

2016-06-15 Fir de Conversatie Christian Brabandt
Am 2016-06-15 23:39, schrieb fritzophrenic: Confirmed, this also affects 7.4.1940, both on 64-bit Windows 7, and on Solaris. Setting the 'regexpengine' to either 1 or 2 also causes the pattern to correctly not match. Can you please set verbose before searching? I wonder if this happens, becau

Re: warning in Windows x86 builds

2016-06-15 Fir de Conversatie Christian Brabandt
Am 2016-06-16 00:49, schrieb Ken Takata: I confirmed that both VC2010 and VC2015 don't warn this. So this would be a problem of VC2013 only. (I haven't tested VC2012.) I don't think we should add the ugly #pragma just for suppressing the warning on VC2013 only. In that case, I agree. Best,

Re: More quickfix test changes

2016-06-15 Fir de Conversatie Yegappan Lakshmanan
Hi Bram, On Wed, Jun 15, 2016 at 1:41 PM, Bram Moolenaar wrote: > > Yegappan Lakshmanan wrote: > >> The attached patch makes the following changes to >> the quickfix tests: >> >> 1. Extends several test cases which currently tests only >> quickfix list to also test location lists. >> 2. Uses

Re: warning in Windows x86 builds

2016-06-15 Fir de Conversatie Ken Takata
Hi, 2016/6/15 Wed 19:36:54 UTC+9 Ken Takata wrote: > Hi Christian and Bram, > > 2016/6/15 Wed 16:04:45 UTC+9 Christian Brabandt wrote: > > Hi Bram! > > > > On Di, 14 Jun 2016, Bram Moolenaar wrote: > > > > > > > > Well, it's computing infinity, so overflow is a bit of an > > > understatement.

Re: Patch 7.4.1926

2016-06-15 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > > Have you tried after patch 7.4.1939? It fixes a problem where > > w_jumplistlen was overwritten with a line number. Valgrind doesn't > > catch this because it's still within a struct. > > I saw that patch, and it looks suspicious, but it was in a different > sect

Re: warning in Windows x86 builds

2016-06-15 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > On Di, 14 Jun 2016, Bram Moolenaar wrote: > > > > > Well, it's computing infinity, so overflow is a bit of an > > understatement. > > Why does only 32bit version complain? > > > > > Perhaps the #ifdef can be adjusted for this compiler and context? > > Perhaps dis

Re: More quickfix test changes

2016-06-15 Fir de Conversatie Bram Moolenaar
Yegappan Lakshmanan wrote: > The attached patch makes the following changes to > the quickfix tests: > > 1. Extends several test cases which currently tests only > quickfix list to also test location lists. > 2. Uses command aliases for quickfix/location list commands, > instead of using

Patch 7.4.1941

2016-06-15 Fir de Conversatie Bram Moolenaar
Patch 7.4.1941 Problem:Not all quickfix tests are also done with the location lists. Solution: Test more quickfix code. Use user commands instead of "exe". (Yegappan Lakshmanan) Files: src/testdir/test_quickfix.vim *** ../vim-7.4.1940/src/testdir/test_quickfix.vim

Re: Patch 7.4.1926

2016-06-15 Fir de Conversatie Christian Brabandt
> Have you tried after patch 7.4.1939? It fixes a problem where > w_jumplistlen was overwritten with a line number. Valgrind doesn't > catch this because it's still within a struct. I saw that patch, and it looks suspicious, but it was in a different section of the file. It still fails after 7.

Re: Patch 7.4.1926

2016-06-15 Fir de Conversatie Dominique Pellé
Bram Moolenaar wrote: > Christian Brabandt wrote: > >> > > On Mo, 13 Jun 2016, Christian Brabandt wrote: >> > > >> > > > Something between 7.4.1924 and 7.4.1926 broke the daily binary built: >> > > > >> > > > ..\gvim -u dos.vim -U NONE --noplugin --not-a-term "+set ff=dos|f >> > > > dostmp\test5

Re: Patch 7.4.1926

2016-06-15 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > > > On Mo, 13 Jun 2016, Christian Brabandt wrote: > > > > > > > Something between 7.4.1924 and 7.4.1926 broke the daily binary built: > > > > > > > > ..\gvim -u dos.vim -U NONE --noplugin --not-a-term "+set ff=dos|f > > > > dostmp\test58.in|wq" test58.in > > > >

Re: Patch 7.4.1926

2016-06-15 Fir de Conversatie Christian Brabandt
On Di, 14 Jun 2016, Bram Moolenaar wrote: > Christian Brabandt wrote: > > > On Mo, 13 Jun 2016, Christian Brabandt wrote: > > > > > Something between 7.4.1924 and 7.4.1926 broke the daily binary built: > > > > > > ..\gvim -u dos.vim -U NONE --noplugin --not-a-term "+set ff=dos|f > > > dostmp\t

Re: [BUG] Patch 7.4.1748 causes infinite loop in 'gd' command

2016-06-15 Fir de Conversatie Bram Moolenaar
Eric Biggers wrote: > Following patch 7.4.1748 (date: 2016-04-16), vim enters an infinite loop when > executing the 'gd' command. This is easy to reproduce. For example, create a > file "test.c" containing the following contents: > > void f(int x) > { > return x; >

Patch 7.4.1940

2016-06-15 Fir de Conversatie Bram Moolenaar
Patch 7.4.1940 Problem:"gd" hangs in some situations. (Eric Biggers) Solution: Remove the SEARCH_START flag when looping. Add a test. Files: src/normal.c, src/testdir/test_goto.vim *** ../vim-7.4.1939/src/normal.c2016-05-24 10:46:41.655541832 +0200 --- src/normal.c201

Patch 7.4.1939

2016-06-15 Fir de Conversatie Bram Moolenaar
Patch 7.4.1939 Problem:Memory access error when reading viminfo. (Dominique Pelle) Solution: Correct index in jumplist when at the end. Files: src/mark.c, src/testdir/test_viminfo.vim *** ../vim-7.4.1938/src/mark.c 2016-06-14 23:02:42.432030667 +0200 --- src/mark.c 2016-06-15 21:19:

Should the alternate file be saved in the session file?

2016-06-15 Fir de Conversatie Victor Haffreingue
Howdy! After experimenting (following a stackoverflow question), it seems that the alternate file is not saved when creating a session with the buffers options is set in sessionoptions. Steps to reproduce: $ touch a $ touch b $ vim -Nu NONE a :e b at this point C-^ will toggle between

Re: &termguicolors is causing display artifacts in the GUI

2016-06-15 Fir de Conversatie Manuel Ortega
On Wed, Jun 15, 2016 at 10:23 AM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > 2016-06-15 23:02 GMT+09:00 Manuel Ortega : > >> On Wed, Jun 15, 2016 at 5:48 AM, Kazunobu Kuriyama < >> kazunobu.kuriy...@gmail.com> wrote: >> >>> I couldn't reproduce the bug with Athena, GTK+ 2, GTK+ 3 GU

Re: &termguicolors is causing display artifacts in the GUI

2016-06-15 Fir de Conversatie Kazunobu Kuriyama
2016-06-15 23:02 GMT+09:00 Manuel Ortega : > On Wed, Jun 15, 2016 at 5:48 AM, Kazunobu Kuriyama < > kazunobu.kuriy...@gmail.com> wrote: > >> I couldn't reproduce the bug with Athena, GTK+ 2, GTK+ 3 GUIs, but did >> with MacVim, although I'm not sure which X11 GUI the reporter meant by that >> doub

Re: &termguicolors is causing display artifacts in the GUI

2016-06-15 Fir de Conversatie Manuel Ortega
On Wed, Jun 15, 2016 at 10:02 AM, Manuel Ortega wrote: > On Wed, Jun 15, 2016 at 5:48 AM, Kazunobu Kuriyama < > kazunobu.kuriy...@gmail.com> wrote: > >> I couldn't reproduce the bug with Athena, GTK+ 2, GTK+ 3 GUIs, but did >> with MacVim, although I'm not sure which X11 GUI the reporter meant by

Re: &termguicolors is causing display artifacts in the GUI

2016-06-15 Fir de Conversatie Manuel Ortega
On Wed, Jun 15, 2016 at 5:48 AM, Kazunobu Kuriyama < kazunobu.kuriy...@gmail.com> wrote: > I couldn't reproduce the bug with Athena, GTK+ 2, GTK+ 3 GUIs, but did > with MacVim, although I'm not sure which X11 GUI the reporter meant by that > doubly quoted word, "regular." I wish the description c

Re: lambda again

2016-06-15 Fir de Conversatie Ken Takata
Hi mattn and all, 2016/5/27 Fri 22:38:34 UTC+9 Ken Takata wrote: > Hi mattn, > > 2016/4/18 Mon 0:30:19 UTC+9 mattn wrote: > > Hi, Bram and list. > > > > Updated lambda patch to be applied for latest code. > > > > https://gist.github.com/mattn/5bc8ded21e1033c9c0ea8cd5ecbbce11 > > > > This inclu

Re: warning in Windows x86 builds

2016-06-15 Fir de Conversatie Ken Takata
Hi Christian and Bram, 2016/6/15 Wed 16:04:45 UTC+9 Christian Brabandt wrote: > Hi Bram! > > On Di, 14 Jun 2016, Bram Moolenaar wrote: > > > > > Well, it's computing infinity, so overflow is a bit of an > > understatement. > > Why does only 32bit version complain? I don't know why, but math.h

Re: &termguicolors is causing display artifacts in the GUI

2016-06-15 Fir de Conversatie Kazunobu Kuriyama
I couldn't reproduce the bug with Athena, GTK+ 2, GTK+ 3 GUIs, but did with MacVim, although I'm not sure which X11 GUI the reporter meant by that doubly quoted word, "regular." I wish the description could be more specific in order to save other devs' time. As to the mentioned "-1H", it looked t

Re: warning in Windows x86 builds

2016-06-15 Fir de Conversatie Christian Brabandt
Hi Bram! On Di, 14 Jun 2016, Bram Moolenaar wrote: > > Well, it's computing infinity, so overflow is a bit of an > understatement. Why does only 32bit version complain? > > Perhaps the #ifdef can be adjusted for this compiler and context? Perhaps disable this specific warning? diff -r 07ee18