Re: [vim/vim] Running :make does not set v:shell_error (#5994)

> I've made things by tweaking `shellpipe` and `makeef` along with a bit > of scripting. > > When opening this I wanted my initial report to be high level. But > getting into the implementation does Vim have to rely on `tee`? I.E. > when invoking `:make` could Vim not read and print the

Re: [vim/vim] Running :make does not set v:shell_error (#5994)

On 2020-04-26, George Brown wrote: > I've made things by tweaking shellpipe and makeef along with a bit of > scripting. > > When opening this I wanted my initial report to be high level. But getting > into > the implementation does Vim have to rely on tee? I.E. when invoking :make > could > Vim

Re: [vim/vim] Running :make does not set v:shell_error (#5994)

On 2020-04-26, Bram Moolenaar wrote: > > > > Works fine for me. What is the command that actually gets executed? > > > It should be something like ":!exit 1 |& tee /tmp/vt42YzR/6" > > > > It is indeed. > > > > > Perhaps your "tee" command does not pass on the exit value > > > > I'm not sure

Patch 8.2.0647

Patch 8.2.0647 Problem:MS-Windows: repeat count for events was not used. Solution: Check the repeat count. (Nobuhiro Takasaki, closes #5989) Files: src/os_win32.c *** ../vim-8.2.0646/src/os_win32.c 2020-04-19 14:02:22.427687032 +0200 --- src/os_win32.c 2020-04-26

Re: [vim/vim] In bash syntax you can't escape a backquote in a double-quoted string. (#5991)

John Little wrote: This is a regression, the syntax/sh.vim from 2019-06-16 does not show this problem. The maintainer of this syntax script has his own version numbering, and if you want to report problems he usually will first ask that you try the latest script from his web site, which is

Patch 8.2.0646

Patch 8.2.0646 Problem:t_Co uses the value of $COLORS in the GUI. (Masato Nishihata) Solution: Ignore $COLORS for the GUI. (closes #5992) Files: src/os_unix.c, src/term.c *** ../vim-8.2.0645/src/os_unix.c 2020-04-14 20:56:27.589970249 +0200 --- src/os_unix.c 2020-04-26

Patch 8.2.0645

Patch 8.2.0645 Problem:MS-Windows terminal: CTRL-C does not get to child job. Solution: Remove CREATE_NEW_PROCESS_GROUP from CreateProcessW(). (Nobuhiro Takasaki, closes #5987) Files: src/terminal.c *** ../vim-8.2.0644/src/terminal.c 2020-04-26 14:47:41.616752488

Patch 8.2.0644

Patch 8.2.0644 Problem:Insufficient testing for invalid function arguments. Solution: Add more tests. (Yegappan Lakshmanan, closes #5988) Files: runtime/doc/eval.txt, src/testdir/test_bufline.vim, src/testdir/test_channel.vim, src/testdir/test_clientserver.vim,

Patch 8.2.0643

Patch 8.2.0643 (after 8.2.0635) Problem:Terminal uses brown instead of dark yellow. (Romain Lafourcade) Solution: Use color index 3 instead of 130. (closes #5993) Files: src/terminal.c *** ../vim-8.2.0642/src/terminal.c 2020-04-12 19:37:13.526297236 +0200 --- src/terminal.c

Patch 8.2.0642

Patch 8.2.0642 Problem:Vim9: using invalid index. Solution: Check index for being valid. Fix memory leak. Files: src/vim9compile.c, src/clientserver.c *** ../vim-8.2.0641/src/vim9compile.c 2020-04-26 13:50:38.432096840 +0200 --- src/vim9compile.c 2020-04-26 14:25:00.255408835

Patch 8.2.0641

Patch 8.2.0641 Problem:Vim9: `=expr` not expanded in :hardcopy and "syntax include". Solution: Add the EX_EXPAND flag. Expend "syntax include". Files: src/ex_cmds.h, src/vim9compile.c, src/vim9execute.c, src/testdir/test_vim9_cmd.vim *** ../vim-8.2.0640/src/ex_cmds.h

Re: [vim/vim] In bash syntax you can't escape a backquote in a double-quoted string. (#5991)

This is a regression, the syntax/sh.vim from 2019-06-16 does not show this problem. The maintainer of this syntax script has his own version numbering, and if you want to report problems he usually will first ask that you try the latest script from his web site, which is version 190. It has