[bug] parsing :command

2015-11-06 Fir de Conversatie LCD 47
To reproduce: function! F() echomsg 'F()' endfunction function! G() echomsg 'G()' endfunction command! F call F() command! G call G() command! FG F|G FG The result of running "FG" is "E488: Trailing characters: F|G". Replacing "F" with its definition helps, running "FG" after

Re: Proposal for new option, 'tagignorecase', with patch

2015-11-06 Fir de Conversatie Gary Johnson
On 2015-11-02, Gary Johnson wrote: > On 2015-11-01, Gary Johnson wrote: > > On 2015-10-30, Bram Moolenaar wrote: > > > Jonathan Newton wrote: > > > > > Do you expect to accept this patch sometime soon? > > > > > > Not sure. We already have so many options... > > > But it does make sense to limi

Re: [BUG] It looks like OOM handling code is harmful

2015-11-06 Fir de Conversatie Nikolay Pavlov
2015-11-06 0:48 GMT+03:00 Bram Moolenaar : > > Nikolay Pavlov wrote: > >> >> Consider the following scenario: while processing function dict_copy >> >> >> >> static dict_T * >> >> dict_copy(orig, deep, copyID) >> >> dict_T *orig; >> >> int deep; >> >>

[patch] command :helpt {dir} leaks memory when directory does not exist

2015-11-06 Fir de Conversatie Dominique Pellé
Hi afl-fuzz found that command :helpt {dir} leaks memory in Vim-7.4.909 when the directory argument does not exist (E150). Valgrind says: ==4962== 2 bytes in 1 blocks are definitely lost in loss record 1 of 125 ==4962==at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.

[bug] access to uninitialized memory in match_backref() regexp_nda.c:4882

2015-11-06 Fir de Conversatie Dominique Pellé
Hi afl-fuzz fuzzer came up with the following command, which causes access to uninitialized memory in Vim-7-4-909: $ valgrind --track-origins=yes 2> valgrind.log \ vim -u NONE -c 'syn keyword x nextgroup=\(\1\)' In valgrind.log: ==4366== Memcheck, a memory error detector ==4366== Copyright (C

Re: [patch] neovim patches

2015-11-06 Fir de Conversatie h_east
Hi Christian and Bram, 2015-11-6(Fri) 19:55:44 UTC+9 h_east: > Hi Christian! > > 2015-11-6(Fri) 17:28:03 UTC+9 Christian Brabandt: > > Bram, > > here is another one (possibly). > > > > https://github.com/neovim/neovim/pull/3614 > > > > Not sure, if this is correct, I ported it to vim, but it di

Re: [vim] 18580 segmentation fault (core dumped) /usr/bin/vimx (#468)

2015-11-06 Fir de Conversatie Olaf Dabrunz
On 06-Nov-15, Christian Brabandt wrote: > > On Mi, 04 Nov 2015, h_east wrote: > > 2015-11-5(Thu) 15:59:29 UTC+9 Christian Brabandt: > > > Hi, > > > > > > what version is this? Can you reproduce this? If so, how? > > > > More information is written to Github page. > > > > Press the following lin

Re: [patch] neovim patches

2015-11-06 Fir de Conversatie h_east
Hi Christian! 2015-11-6(Fri) 17:28:03 UTC+9 Christian Brabandt: > Bram, > here is another one (possibly). > > https://github.com/neovim/neovim/pull/3614 > > Not sure, if this is correct, I ported it to vim, but it didn't seem to > have any effect. > > If anybody has a test case¹, that works, I

Re: [vim] 18580 segmentation fault (core dumped) /usr/bin/vimx (#468)

2015-11-06 Fir de Conversatie Christian Brabandt
On Mi, 04 Nov 2015, h_east wrote: > 2015-11-5(Thu) 15:59:29 UTC+9 Christian Brabandt: > > Hi, > > > > what version is this? Can you reproduce this? If so, how? > > More information is written to Github page. > > Press the following link of the first post of this thread. "view it on GitHub" Tha

Re: [patch] neovim patches

2015-11-06 Fir de Conversatie Christian Brabandt
Bram, here is another one (possibly). https://github.com/neovim/neovim/pull/3614 Not sure, if this is correct, I ported it to vim, but it didn't seem to have any effect. If anybody has a test case¹, that works, I'd like to hear so I can port it to vim and add a test. ¹) I tried with the exam