| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
This reverts commit 278c5d452c2cbc436a9cc317407ae6021a226c3a.
|
| |
|
|
|
|
| |
This shows them also with test failures/errors, where it is useful to
see how long the test took (for flaky failures running into timeout).
|
|
|
| |
This is used internally (e.g. on Travis) for 32-bit builds (`-m32`).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Those are flaky when using luacov (which causes reproducible slowness).
E.g.:
[ ERROR ] test/functional\eval\timer_spec.lua @ 105: timers can invoke redraw in blocking getchar() call
test\functional\ui\screen.lua:587: Row 3 did not match.
Expected:
|ITEM 1 |
|ITEM 2 |
|*{1:~ }|
|{1:~ }|
|{1:~ }|
|^ |
Actual:
|ITEM 1 |
|ITEM 2 |
|*ITEM 3 |
|{1:~ }|
|{1:~ }|
|^ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Doing the screen test first might give insights about a possible
(flaky?) failure, where it looks like "feed_data" is processed out of
order:
[ ERROR ] test/functional/terminal/tui_spec.lua @ 561: TUI paste: exactly 64 bytes #10311
test/functional/helpers.lua:388:
retry() attempts: 490
test/functional/terminal/tui_spec.lua:66: Expected objects to be the same.
Passed in:
(table: 0x44042de8) {
*[1] = ' endzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz' }
Expected:
(table: 0x41d6e568) {
*[1] = 'zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz end' }
stack traceback:
test/functional/helpers.lua:388: in function 'retry'
test/functional/terminal/tui_spec.lua:63: in function 'expect_child_buf_lines'
test/functional/terminal/tui_spec.lua:569: in function <test/functional/terminal/tui_spec.lua:561>
Ref: https://github.com/neovim/neovim/pull/11083#issuecomment-534375201
Build log: https://travis-ci.org/neovim/neovim/jobs/588749739#L5597
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids having a dummy event to tickle the main loop.
Confirmed using `nvim -u NONE -c 'au FocusGained * q'` in tmux (with
`:set -g focus-events on`): without the flushing it would only exit
after pressing a key.
Moves the flushing done recently in 3626d2107.
`nvim -u NONE -cq` is still working (i.e. consuming the response for the
terminal background query itself), and the flickering mentioned in
3626d2107 is reduced again.
Reverts part of bfb21f3e0 (#7729).
|
|
|
|
|
| |
Problem: ex_helpgrep() is too long.
Solution: Refactor the function. (Yegappan Lakshmanan, closes vim/vim#2766)
https://github.com/vim/vim/commit/2225ebb48644f3924311b8df02a1319ab7675d42
|
|
|
|
|
| |
Problem: The qf_jump_to_usable_window() function is too long.
Solution: Split it in parts. (Yegappan Lakshmanan, closes vim/vim#2891)
https://github.com/vim/vim/commit/7a2b0e55e9460493c4a949bda8be70950dbb8f85
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This aligns with `terminfo_stop`, which also flushes the buffer
after disabling things.
This ensures Neovim gets the response to the terminal background query
before exiting (`nvim -u NONE -cq` with e.g. urxvt or kitty).
Caveats:
* With kitty this causes some "flickering", likely since the alternate
screen is being setup with `nvim -u NONE -cq`, whereas it would not be
processed otherwise before quitting (as with the background query).
* tmux after this patch may print ^[[I (CSI I / FocusGained) after
`nvim -u NONE -cq`.
Fixes https://github.com/neovim/neovim/issues/11062
|
|\
| |
| |
| | |
Fix fold patches: vim-patch:8.1.2052, vim-patch:8.1.2059
fix #11002
|
| |
| |
| |
| |
| |
| | |
Problem: Fix for "x" deleting a fold has side effects.
Solution: Fix it where the fold is included.
https://github.com/vim/vim/commit/56ebbabea1d8409ba67127b9674f6c714739c8e0
|
|/
|
|
|
|
| |
Problem: Using "x" before a closed fold may delete that fold.
Solution: Do not translate 'x' do "dl". (Christian Brabandt, closes vim/vim#4927)
https://github.com/vim/vim/commit/7a9bd7c1e0ce1baf5a02daf36eeae3638aa315c7
|
| |
|
| |
|
|\
| |
| | |
screen: missing redraw/highlight for ruler in message area
|
|/ |
|
|
|
|
|
|
|
|
| |
Problem: ":lang messages en_US.UTF-8" no longer overrides the language
detected from the environment (at startup).
Solution: In os_setenv, special-case "LC_ALL", "LANG", et al. to use
putenv_s instead of uv_os_setenv.
fixes #11045
|
|\
| |
| | |
Fix "precedes" listchar behavior in wrap mode
|
| |
| |
| |
| |
| |
| |
| |
| | |
(Credit: Zach Wegner, https://github.com/neovim/neovim/pull/11034)
Problem: "precedes" in 'listchars' not used properly.
Solution: Correctly handle the "precedes" char in list mode for long lines.
https://github.com/vim/vim/commit/bffba7f7042f6082e75b42484b15f66087b01941
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Previously, the "precedes" character would be rendered on every row
when w_skipcol > 0 (i.e., when viewing a single line longer than the
entire screen), instead of just on the first row. Make sure to only
render it on the first row in this case.
Add a test for this behavior.
Fix documentation for the "precedes" character, which erroneously
stated that it was only active when wrap mode was off.
|
|
|
| |
close #11040
|
|
|
|
|
|
| |
Problem: Not easy to jump to function line from profile.
Solution: Use "file:99" instead of "file line 99" so that "gf" works.
(Daniel Hahler, closes vim/vim#4951)
https://github.com/vim/vim/commit/181d4f58cc421f2e6d3b16333d4cb70d35ad1342
|
|\
| |
| | |
vim-patch:8.0.{1109,1529,1539,1621,1733,1771,1776},8.1.{1783,2054,2058}
|
| |
| |
| |
| |
| |
| | |
Problem: Using invalid default value for highlight attribute.
Solution: Use zero instead of -1.
https://github.com/vim/vim/commit/6185903e3d07eb53326fc1403fc2de97ca31b775
|
| |
| |
| |
| |
| |
| | |
Problem: Assert_equalfile() does not close file descriptors. (Coverity)
Solution: Close the file descriptors.
https://github.com/vim/vim/commit/3049418f3dbc571463a04d068069f6c5b7a8ccf1
|
| |
| |
| |
| |
| |
| | |
Problem: In tests, when WaitFor() fails it doesn't say why.
Solution: Turn a few more WaitFor() into WaitForAssert().
https://github.com/vim/vim/commit/0e9d1ae3216a5940b36bb56d155fb300b2e55b00
|
| |
| |
| |
| |
| |
| | |
Problem: In tests, when WaitFor() fails it doesn't say why. (James McCoy)
Solution: Add WaitForAssert(), which produces an assert error when it fails.
https://github.com/vim/vim/commit/50182fa84e20a0547f3e2bd6683ef799fcd27855
|
| |
| |
| |
| |
| |
| | |
Problem: Incomplete testing for completion fix. (Lifepillar)
Solution: Add a test with CTRL-P.
https://github.com/vim/vim/commit/bad0ce7b26be5eed8524347018f4c835b212f8d1
|
| |
| |
| |
| |
| |
| | |
Problem: No test for the popup menu positioning.
Solution: Add a screendump test for the popup menu.
https://github.com/vim/vim/commit/6bb2cdfe604e51eec216cbe23bb6e8fb47810347
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Timer causes error on exit from Ex mode. (xtal8)
Solution: save and restore the ex_pressedreturn flag. (Christian Brabandt,
closes vim/vim#2079)
https://github.com/vim/vim/commit/f5291f301e9322545f0621b2157e93050d1d4fb3
|
| |
| |
| |
| |
| |
| | |
Problem: Function for ex command is named inconsistently.
Solution: Rename do_marks() to ex_marks().
https://github.com/vim/vim/commit/4bd782339e370bde82c2a8976df9f335cc12eba9
|
| |
| |
| |
| |
| |
| | |
Problem: Compiler test for Perl may fail.
Solution: Accept any error line number. (James McCoy, closes vim/vim#4944)
https://github.com/vim/vim/commit/cebfcffa40c058119bc2f92f0db02dffd3f6affe
|
| |
| |
| |
| |
| |
| | |
Problem: MS-Windows: compiler test may fail when using %:S.
Solution: Reset 'shellslash'.
https://github.com/vim/vim/commit/dff2adc8ddcb6c8f3390a82c321362f8d6756fb8
|
|/
|
|
|
| |
Problem: assert_fails() does not take a message argument
Solution: Add the argument.
https://github.com/vim/vim/commit/1307d1c003b01b4f67524c95feb07c3d91c7c428
|
|\
| |
| | |
screen: fix vcol counting with virtual text.
|
|/ |
|
|\
| |
| | |
Vim patches for indent tests
|
| |
| |
| |
| |
| |
| | |
Problem: "make test" for indent files doesn't cause make to fail.
Solution: Exit the script with ":cquit". (Daniel Hahler, closes vim/vim#4949)
https://github.com/vim/vim/commit/cd67059c0c3abf1e28aa66458abdf6f338252eb2
|
| |
| |
| |
| | |
Several runtime updates ignored the non-existing files.
|
| |
| |
| |
| |
| |
| |
| | |
Problem: "make clean" in top dir does not cleanup indent test output.
Solution: Clean the indent test output. Do not rely on the vim executable
for that. (closes vim/vim#4307)
https://github.com/vim/vim/commit/e13a3901cae0afb4d2af30d497696af08029fd81
|
| |
| |
| |
| |
| |
| | |
Problem: Without the +eval feature the indent tests don't work.
Solution: Skip the body of the tests.
https://github.com/vim/vim/commit/eeed665b0ecd917e88e3475c9615d52546aa124d
|
| |
| |
| |
| |
| |
| | |
Problem: Indent script tests pick up installed scripts.
Solution: Use current runtime indent scripts.
https://github.com/vim/vim/commit/30700cd5ffa258f1d684ab6b34bd03e970450dba
|
| |
| |
| |
| |
| |
| | |
Problem: When executing indent tests user preferences interfere.
Solution: Add "--clean".
https://github.com/vim/vim/commit/dc2f73a6980be13c97a83047d0de50824bc0f20f
|
|/
|
|
|
|
|
| |
Problem: No tests for indent files.
Solution: Add a mechanism for running indent file tests. Add a first test
for Vim indenting.
https://github.com/vim/vim/commit/c0fe4978f2311be9a0221d4c2369251c719b399a
|
|
|
|
|
|
|
| |
Before 6e9ea5adc `win_ins_lines` would return `FAIL` for `i/line_count == 0`.
Handle this by checking it in the outer `if`.
Ref: https://github.com/neovim/neovim/commit/6e9ea5ad#commitcomment-35084669
|
|
|
| |
Ref: https://github.com/neovim/neovim/pull/11047#issuecomment-532268826
|
|\
| |
| | |
vim-patch:8.0.{1523,1770}
|
| |
| |
| |
| |
| |
| | |
Problem: Assert functions don't return anything.
Solution: Return non-zero when the assertion fails.
https://github.com/vim/vim/commit/65a5464985f980d2bbbf4e14d39d416dce065ec7
|