Patch 8.2.0177

2020-01-29 Fir de Conversatie Bram Moolenaar
Patch 8.2.0177 Problem:Memory leak in get_tags(). Solution: Free matches when finding a pseudo-tag line. (Dominique Pelle, closes #5553) Files: src/tag.c *** ../vim-8.2.0176/src/tag.c 2020-01-26 21:59:25.632718110 +0100 --- src/tag.c 2020-01-29 22:37:01.585373712

Patch 8.2.0176

2020-01-29 Fir de Conversatie Bram Moolenaar
Patch 8.2.0176 Problem:Generating os headers does not work for Swedish. Solution: Set the locale to C. (Christian Brabandt, closes #5258) Files: src/osdef.sh *** ../vim-8.2.0175/src/osdef.sh2016-01-23 22:40:21.0 +0100 --- src/osdef.sh2020-01-29

Patch 8.2.0175

2020-01-29 Fir de Conversatie Bram Moolenaar
Patch 8.2.0175 Problem:Crash when removing list element in map(). Solution: Lock the list. (closes #2652) Files: src/testdir/test_filter_map.vim, src/list.c *** ../vim-8.2.0174/src/testdir/test_filter_map.vim 2019-09-03 16:50:08.0 +0200 ---

Re: uppercase meta maps in xterm vim

2020-01-29 Fir de Conversatie Bram Moolenaar
Pavol Juhas wrote: > I am using a fairly recent XTerm(348) on Debian linux. > I have noticed that the modifyOtherKeys feature in vim > makes mappings of meta keys (produced with Alt modifier) > work out of the box, for example, `map :echo "meta-a"`. > This however seems to work only for

Re: [patch] fixed typos in runtime/doc/vim9.txt

2020-01-29 Fir de Conversatie Bram Moolenaar
Dominique wrote: > Attached patch fixes typos in runtime/doc/vim9.txt Thanks. -Specifically, an empty list is falsey. +Specifically, an empty list is false. "falsey" is correct, search for "Falsey values in JavaScript". -- hundred-and-one symptoms of being an internet addict: 10. And even

Patch 8.2.0174

2020-01-29 Fir de Conversatie Bram Moolenaar
Patch 8.2.0174 Problem:Various commands not completely tested. Solution: Add more test cases. (Yegappan Lakshmanan, closes #5551) Files: src/testdir/test_excmd.vim, src/testdir/test_fnameescape.vim, src/testdir/test_ga.vim, src/testdir/test_global.vim,

Re: [BUG] Confusing behavior of the char_avail() function breaks titlestring

2020-01-29 Fir de Conversatie Jason Franklin
On Wednesday, January 29, 2020 at 3:28:06 PM UTC-5, Bram Moolenaar wrote: > > > Possibly Vim asks the terminal for the version, and the response can be > read from the input. You could make t_RV empty to avoid that. > I don't think this is the right fix. NeoVim doesn't have this problem for

Re: [BUG] Confusing behavior of the char_avail() function breaks titlestring

2020-01-29 Fir de Conversatie Bram Moolenaar
Jason Franklin wrote: > I discovered a bug a while ago that can be observed in xterm, > gnome-terminal, > and konsole (on KDE). > > To reproduce the bug, with the latest build... > > 1. cd src/ > 2. VIMRUNTIME=../runtime ./vim -u NONE --cmd 'set nocp lz title' > 3. note that the title string

Re: Compile errors on HP-UX after 8.2.0149

2020-01-29 Fir de Conversatie Bram Moolenaar
John Marriott wrote: > I just applied patches 8.2.0148 to 8.2.0162 to the sources on my work > HP-UX machine and tried to compile. The build failed with this error: > > Starting make in the src directory. > If there are problems, cd to the src directory and run make there >     cd src &&

Patch 8.2.0173

2020-01-29 Fir de Conversatie Bram Moolenaar
Patch 8.2.0173 Problem:Build fails with old compiler. Solution: Do not use anonymous unions. (John Marriott) Files: src/vim9compile.c, src/evalvars.c, src/list.c, src/structs.h, src/evalfunc.c, src/channel.c, src/if_mzsch.c, src/if_py_both.h ***

[BUG] Confusing behavior of the char_avail() function breaks titlestring

2020-01-29 Fir de Conversatie Jason Franklin
Greetings: I discovered a bug a while ago that can be observed in xterm, gnome-terminal, and konsole (on KDE). To reproduce the bug, with the latest build... 1. cd src/ 2. VIMRUNTIME=../runtime ./vim -u NONE --cmd 'set nocp lz title' 3. note that the title string is not drawn, also, possibly,

Re: [vim/vim] empty search repeats the previous search, yet drops the leading empty space (#5550)

2020-01-29 Fir de Conversatie Gary Johnson
On 2020-01-29, MontrealSergiy wrote: > What gvim is doing I do not understand well but I imagine gvim is > not supposed fully support vim features as it concentrates on GUI > UX No, as long as they are built with the same features enabled, their behaviors should be nearly identical, the only

Re: uppercase meta maps in xterm vim

2020-01-29 Fir de Conversatie Pavol Juhas
On Tue, Jan 28, 2020 at 10:24 PM Tony Mechelynck < antoine.mechely...@gmail.com> wrote: ... > The problem is that when running Vim in a console (as opposed to gvim) > any keys and key combos you hit have to go through a console interface > before they reach Vim… or don't. Some of these are passed