Re: [bug] invalid memory access with normal commands

Hi Dominique! On Di, 14 Feb 2017, Dominique Pellé wrote: > Hi > > afl-fuzz found another command that causes access to > invalid memory in Vim-8.0.329. It's not a recent regression > since bug is present in at least Vim-7.4.52 that comes > with ubuntu-14.04. > > I have not been able to find a

Re: _UI64_MAX build error

On Tue, Feb 14, 2017 at 10:29 PM, Ken Takata wrote: > 2017/2/15 Wed 11:05:21 UTC+9 Steve Hall wrote: > > > > i686-pc-mingw32-gcc -c -Iproto -DWIN32 -DWINVER=0x0501 > > This shows that the setting of CROSS_COMPILE is not overwritten. I > think that setting a variable in a

Re: _UI64_MAX build error

Hi, 2017/2/15 Wed 11:05:21 UTC+9 Steve Hall wrote: > On Tue, Feb 14, 2017 at 6:56 PM, Ken Takata wrote: > > 2017/2/15 Wed 5:43:08 UTC+9 Steve Hall wrote: > > > > > > I'm setting the environment elsewhere now. So the only other thing in > > > Make_cyg is UNDER_CYGWIN = yes.

Re: _UI64_MAX build error

On Tue, Feb 14, 2017 at 6:56 PM, Ken Takata wrote: > 2017/2/15 Wed 5:43:08 UTC+9 Steve Hall wrote: > > > > I'm setting the environment elsewhere now. So the only other thing in > > Make_cyg is UNDER_CYGWIN = yes. Not sure what that does, is it > > important? > > It is used

Re: [vim/vim] open grep result directly (#1473)

Hi Bram, On Tue, Feb 14, 2017 at 2:50 PM, Bram Moolenaar wrote: > > Yegappan Lakshmanan wrote: > >> On Mon, Feb 13, 2017 at 3:22 PM, Bram Moolenaar >> wrote: >> > It's possible in various ways, but still requires the user to add a mapping >> > or

Re: _UI64_MAX build error

Hi, 2017/2/15 Wed 5:43:08 UTC+9 Steve Hall wrote: > On Tue, Feb 14, 2017 at 9:58 AM, Ken Takata wrote: > > > 2017/2/14 Tue 22:58:45 UTC+9 Steve Hall wrote: > > > > > > I'm was simply using "make -f Make_cyg.mak", that was the default. > > > > Hmm, did you set 'ARCH=x86-64'

Re: [patch] Remove "VimL" and like word from Vim source tree

Hirohito Higashi wrote: > Hi Bram, Dr.Chip and list, > > I removed "VimL" and like word from Vim source tree. > > Related comment: > https://groups.google.com/d/msg/vim_dev/3Z5yM8KER2w/wAqws0QSEAAJ > > Please check an attached patch. Thanks! Didn't realize we had so many of these already.

Re: [vim/vim] open grep result directly (#1473)

Yegappan Lakshmanan wrote: > On Mon, Feb 13, 2017 at 3:22 PM, Bram Moolenaar > wrote: > > It's possible in various ways, but still requires the user to add a mapping > > or autocommand. > > Problem is always that a file name could actually end in :{number}. > > > > I

Re: Patch 8.0.0329

2017-02-15 4:48 GMT+09:00 Bram Moolenaar : > > Kazunobu Kuriyama wrote: > > > > Dominique wrote: > > > > > > > Bram Moolenaar wrote: > > > > > > > > > Patch 8.0.0329 > > > > > Problem:Xfontset and guifontwide are not tested. > > > > > Solution: Add tests. (Kazunobu

Re: Patch 8.0.0329

2017-02-15 4:10 GMT+09:00 Dominique Pellé : > Kazunobu Kuriyama wrote: > > > 2017-02-14 5:43 GMT+09:00 Dominique Pellé : > >> > >> Bram Moolenaar wrote: > >> > >> > Patch 8.0.0329 > >> > Problem:Xfontset and guifontwide are not tested. >

Re: _UI64_MAX build error

On Tue, Feb 14, 2017 at 9:58 AM, Ken Takata wrote: > 2017/2/14 Tue 22:58:45 UTC+9 Steve Hall wrote: > > > > I'm was simply using "make -f Make_cyg.mak", that was the default. > > Hmm, did you set 'ARCH=x86-64' manually? > The command line you pasted has '-march=x86-64'.

[bug] invalid memory access with normal commands

Hi afl-fuzz found another command that causes access to invalid memory in Vim-8.0.329. It's not a recent regression since bug is present in at least Vim-7.4.52 that comes with ubuntu-14.04. I have not been able to find a fix yet. Step to reproduce: $ valgrind vim -u NONE -c'norm oxx' -c'norm

Re: Patch 8.0.0329

Kazunobu Kuriyama wrote: > > Dominique wrote: > > > > > Bram Moolenaar wrote: > > > > > > > Patch 8.0.0329 > > > > Problem:Xfontset and guifontwide are not tested. > > > > Solution: Add tests. (Kazunobu Kuriyama) > > > > Files: src/testdir/test_gui.vim > > > > > > A test introduced by

Re: [patch] Remove "VimL" and like word from Vim source tree

h_east wrote: > Hi Bram, Dr.Chip and list, > > I removed "VimL" and like word from Vim source tree. > > Related comment: > https://groups.google.com/d/msg/vim_dev/3Z5yM8KER2w/wAqws0QSEAAJ > > Please check an attached patch. > > >> Dr.Chip (as a netrw author) > There is also a "VimL" word in the

Re: [vim/vim] open grep result directly (#1473)

Hi, On Mon, Feb 13, 2017 at 2:13 AM, was wrote: > Thanks @chrisbra, I did not even hear of quickfix/location, I need some more > googling and reading. > > I used to: > > git grep -n foo > no results found or not what I expect, then git grep -n bar > use vim for a

Re: _UI64_MAX build error

Hi, 2017/2/14 Tue 22:58:45 UTC+9 Steve Hall wrote: > On Mon, Feb 13, 2017 at 6:15 PM, Ken Takata wrote: > > > > Are you really using i686-pc-mingw32-gcc for x64 build? > > > I'm was simply using "make -f Make_cyg.mak", that was the default. Hmm, did you set

Re: _UI64_MAX build error

On Mon, Feb 13, 2017 at 6:15 PM, Ken Takata wrote: > > Are you really using i686-pc-mingw32-gcc for x64 build? I'm was simply using "make -f Make_cyg.mak", that was the default. > It is a compiler for x86 build. You should use > x86_64-w64-mingw32-gcc for x64 build. Set

Re: [vim/vim] The scroll does not keep up the cursor on some situation. (#1474)

On 2017-02-13, 23:41 GMT, Bram Moolenaar wrote: > I think what you are seeing here is intentional. When you > type exactly the characters that fit, Vim won't scroll the > display up until you type another character. It's not really > a problem, right? I am not sure whether it is the same,

[patch] Remove "VimL" and like word from Vim source tree

Hi Bram, Dr.Chip and list, I removed "VimL" and like word from Vim source tree. Related comment: https://groups.google.com/d/msg/vim_dev/3Z5yM8KER2w/wAqws0QSEAAJ Please check an attached patch. > Dr.Chip (as a netrw author) There is also a "VimL" word in the help of netrw. I hope you accept

Re: Patch 8.0.0329

2017-02-14 8:42 GMT+09:00 Bram Moolenaar : > > Dominique wrote: > > > Bram Moolenaar wrote: > > > > > Patch 8.0.0329 > > > Problem:Xfontset and guifontwide are not tested. > > > Solution: Add tests. (Kazunobu Kuriyama) > > > Files: src/testdir/test_gui.vim > > > > A