Re: [vim/vim] New search is horrible and difficult to disable (MINT19) (#3663)

i apologize for not following this sooner, but i build my own vim and i have a vimrc so i never noticed it was happening i would have voted to have noincsearch be the default had i been paying attention -- incsearch would be horribly hard to live with and i don't get why anyone would want it

Re: Patch 8.1.0565

Bram Moolenaar wrote: > I wrote: > > > Patch 8.1.0565 > > Problem:Asan complains about reading before allocated block. > > Solution: Workaround: Avoid offset from becoming negative. > > Files:src/gui.c > > > > > > *** ../vim-8.1.0564/src/gui.c 2018-11-16 16:21:01.633310065 +0100

Re: Patch 8.1.0565

Tony wrote: > On Wed, Dec 5, 2018 at 7:46 PM Bram Moolenaar wrote: > > > > > > Patch 8.1.0565 > > Problem:Asan complains about reading before allocated block. > > Solution: Workaround: Avoid offset from becoming negative. > > Files: src/gui.c > [...] > > ! // FIXME: how

Re: Patch 8.1.0565

I wrote: > Patch 8.1.0565 > Problem:Asan complains about reading before allocated block. > Solution: Workaround: Avoid offset from becoming negative. > Files:src/gui.c > > > *** ../vim-8.1.0564/src/gui.c 2018-11-16 16:21:01.633310065 +0100 > --- src/gui.c 2018-12-05

Re: [vim/vim] quickfix: vcol only appears to handle tabs (#3658)

Hi, On Wed, Dec 5, 2018 at 12:50 PM Bram Moolenaar wrote: > > > The help for vcol says: > > > > > vcol |TRUE|: "col" is visual column > > > |FALSE|: "col" is byte index > > You mean the help for getqflist() and setqflist(). > > > But it appears to only handle tab characters: > >

Re: [Question] Stripping of Vim binaries

On Wed, Dec 05, 2018 at 09:28:05AM -0800, zdoh...@redhat.com wrote: > I looked into Vim's Makefile and I found out binary stripping happens > during the built, which causes missing debuginfo data in the end of > the build. > Would someone mind telling me if there a reason why stripping is done? >

Re: Patch 8.1.0565

On Wed, Dec 5, 2018 at 7:46 PM Bram Moolenaar wrote: > > > Patch 8.1.0565 > Problem:Asan complains about reading before allocated block. > Solution: Workaround: Avoid offset from becoming negative. > Files: src/gui.c [...] > ! // FIXME: how can the first character ever be

Patch 8.1.0565

Patch 8.1.0565 Problem:Asan complains about reading before allocated block. Solution: Workaround: Avoid offset from becoming negative. Files: src/gui.c *** ../vim-8.1.0564/src/gui.c 2018-11-16 16:21:01.633310065 +0100 --- src/gui.c 2018-12-05 19:44:07.455956642 +0100

Re: [Question] Stripping of Vim binaries

On Wed, Dec 5, 2018 at 6:28 PM wrote: > > Hi, > > I looked into Vim's Makefile and I found out binary stripping happens during > the built, which causes missing debuginfo data in the end of the build. > Would someone mind telling me if there a reason why stripping is done? Is > there a way how

Patch 8.1.0564

Patch 8.1.0564 Problem:Setting v:errors to wrong type still possible. Solution: Return after giving an error message. (Christian Brabandt) Files: src/eval.c, src/testdir/test_eval_stuff.vim *** ../vim-8.1.0563/src/eval.c 2018-12-04 22:37:46.122286870 +0100 --- src/eval.c

Re: Patch 8.1.0563

Christian wrote: > On Di, 04 Dez 2018, Bram Moolenaar wrote: > > > > > Patch 8.1.0563 > > Problem:Setting v:errors to a string give confusing error. (Christian > > Brabandt) > > Solution: Change internal error into normal error message. > > Files: src/eval.c > >

[Question] Stripping of Vim binaries

Hi, I looked into Vim's Makefile and I found out binary stripping happens during the built, which causes missing debuginfo data in the end of the build. Would someone mind telling me if there a reason why stripping is done? Is there a way how to disable stripping during build? I didn't find any