Vimgrep may add results to a wrong quickfix list

2018-03-25 Fir de Conversatie Yegappan Lakshmanan
Hi, When developing tests for autocmds changing the quickfix/location lists when vimgrep is running, I noticed that in some cases vimgrep may add results to a wrong quickfix list. The attached patch fixes this problem by using the quickfix list identifier and adds a test. - Yegappan -- -- You

Re: Test_terminal_response_to_control_sequence still failing for me

2018-03-25 Fir de Conversatie Bram Moolenaar
> I've been watching and no-one else seems to be reporting a > problem with this test -- it's been failing for me > consistently for several weeks > > function RunTheTest[38]..Test_terminal_response_to_control_sequence line > 17: Pattern '\\<\\d\\+R' does not match 'sh-4.3$ R' > > question: doe

Patch 8.0.1645

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1645 Problem:Test for terminal response to escape sequence fails for some people. (toothpik) Solution: Run "cat" and let it echo the characters. Files: src/testdir/test_terminal.vim *** ../vim-8.0.1644/src/testdir/test_terminal.vim 2018-03-25 20:31:28.9646

Patch 8.0.1644

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1644 Problem:Terminal API tests still fail. Solution: Explicitly set 'title' in the terminal job. (Ozaki Kiichi, closes #2750) Files: src/testdir/test_terminal.vim, src/testdir/screendump.vim *** ../vim-8.0.1643/src/testdir/test_terminal.vim 2018-03-25 19:

Test_terminal_response_to_control_sequence still failing for me

2018-03-25 Fir de Conversatie tooth pik
I've been watching and no-one else seems to be reporting a problem with this test -- it's been failing for me consistently for several weeks function RunTheTest[38]..Test_terminal_response_to_control_sequence line 17: Pattern '\\<\\d\\+R' does not match 'sh-4.3$ R' question: does this test make

Re: Patch 8.0.1641

2018-03-25 Fir de Conversatie Elimar Riesebieter
* Bram Moolenaar [2018-03-25 18:58 +0200]: > > Elimar - > > > test fails as follows: > > > > * Bram Moolenaar [2018-03-25 18:20 +0200]: > > > > > > > > Patch 8.0.1641 > > > Problem:Job in terminal can't communicate with Vim. > > > Solution: Add the terminal API. > > > Files: src/

Patch 8.0.1643

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1643 Problem:Terminal API tests fail. Solution: Explicitly set 'title'. Files: src/testdir/test_terminal.vim *** ../vim-8.0.1642/src/testdir/test_terminal.vim 2018-03-25 18:56:20.236729661 +0200 --- src/testdir/test_terminal.vim 2018-03-25 19:08:47.012458600 +02

Patch 8.0.1642

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1642 Problem:Running Vim in terminal fails with two windows. Solution: Pass the number of rows to RunVimInTerminal(). Files: src/testdir/screendump.vim, src/testdir/test_terminal.vim *** ../vim-8.0.1641/src/testdir/screendump.vim 2018-03-25 18:19:47.221066088 +0200 --- src

Patch 8.0.1641

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1641 Problem:Job in terminal can't communicate with Vim. Solution: Add the terminal API. Files: src/terminal.c, src/buffer.c, src/testdir/test_terminal.vim, src/testdir/screendump.vim, runtime/doc/terminal.txt *** ../vim-8.0.1640/src/terminal.c 2018-03-23 22

Patch 8.0.1640

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1640 Problem:Test_cwd() is flaky. Solution: Add to list of flaky tests. Files: src/testdir/runtest.vim *** ../vim-8.0.1639/src/testdir/runtest.vim 2018-02-12 21:31:29.678121098 +0100 --- src/testdir/runtest.vim 2018-03-25 17:12:45.115753832 +0200 *** ***

Patch 8.0.1639

2018-03-25 Fir de Conversatie Bram Moolenaar
Patch 8.0.1639 Problem:Libvterm code lags behind master. Solution: Sync to head, solve merge problems. Files: src/libvterm/README, src/libvterm/bin/unterm.c, src/libvterm/bin/vterm-ctrl.c, src/libvterm/bin/vterm-dump.c, src/libvterm/doc/URLs, src/libvterm/doc/seq

Re: term-dump differences

2018-03-25 Fir de Conversatie Christian Brabandt
On Sa, 24 Mär 2018, Bram Moolenaar wrote: > > On Fr, 23 Mär 2018, Christian Brabandt wrote: > > > > On Fr, 23 Mär 2018, Bram Moolenaar wrote: > > > > > > > Weird. I can only explain it if the dump that has @32 had a NUL > > > > character in there. Both NUL and space end up as a space in the