| Commit message (Collapse) | Author | Age |
... | |
| |\
| | |
| | | |
vim-patch:8.2.{5120.5121}
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Interrupt test sometimes fails.
Solution: Use a different file name.
https://github.com/vim/vim/commit/8d6420631c2bd73dbc1939c4bf04ab7bb39cc263
Add a modeline to test_interrupt.vim.
|
| |/
| |
| |
| |
| |
| | |
Problem: Searching for quotes may go over the end of the line.
Solution: Check for running into the NUL.
https://github.com/vim/vim/commit/2f074f4685897ab7212e25931eeeb0212292829f
|
| |
| |
| |
| |
| | |
Problem: "limit" option of matchfuzzy() not always respected.
Solution: Remove "else". (Kazuyuki Miyagi, closes vim/vim#10586)
https://github.com/vim/vim/commit/47f1a55849a73cefe738a246798221e45448546a
|
| |
| |
| |
| | |
Update runtime files
https://github.com/vim/vim/commit/d592deb336523a5448779ee3d4bba80334cff1f7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #18980
- 831fa45ad84e is related but this doesn't regress that
- The `cterm_normal_fg_color != ae.cterm_fg_color` comparison is originally
carried from patch to patch starting all the way back in 29bc6dfabde2 where it
was avoiding setting a HL attr. But `hlattrs2dict()` now is just
informational.
|
| |
| |
| | |
add benchmark from #18109
|
| |
| |
| |
| |
| |
| | |
The current emulation script enters Insert mode much too frequently.
Using only BufWinEnter seems to be a closer simulation.
Also add a few more mappings.
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem:
- Unix sockets are created in random /tmp dirs.
- /tmp is messy, unclear when OSes actually clear it.
- The generated paths are very ugly. This adds friction to reasoning
about which paths belong to which Nvim instances.
- No way to provide a human-friendly way to identify Nvim instances in
logs or server addresses.
Solution:
- Store unix sockets in stdpath('state')
- Allow --listen "name" and serverstart("name") to given a name (which
is appended to a generated path).
TODO:
- is stdpath(state) the right place?
|
| | |
| | |
| | |
| | |
| | | |
Don't need to dumplog() on each failed test because we now have test-ids
that associate log messages with tests.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem:
1. Log messages (especially in CI) are hard to correlate with tests.
2. Since b353a5c05f02 #11886, dumplog() prints the logs next to test
failures. This is noisy and gets in the way of the test results.
Solution:
1. Associate an incrementing id with each test and include it in log
messages.
- FUTURE: add v:name so Nvim instances can be formally "named"?
2. Mention "child" in log messages if the current Nvim is a child (based
on the presence of $NVIM).
BEFORE:
DBG … 12345 UI: event
DBG … 12345 log_server_msg:722: RPC ->ch 1: …
DBG … 12345 UI: flush
DBG … 12345 inbuf_poll:444: blocking... events_enabled=1 events_pending=0
DBG … 23454 UI: stop
INF … 23454 os_exit:594: Nvim exit: 0
AFTER:
DBG … T57 UI: event
DBG … T57 log_server_msg:722: RPC ->ch 1: …
DBG … T57 UI: flush
DBG … T57 inbuf_poll:444: blocking... events_enabled=1 events_pending=0
DBG … T57/child UI: stop
INF … T57/child os_exit:594: Nvim exit: 0
|
| |\ \
| | | |
| | | | |
fix(treesitter): new iter if folded
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | | |
Problem: Icon filetype not recognized from the first line.
Solution: Add a check for the first line. (Doug Kearns)
https://github.com/vim/vim/commit/bf6614643f656d38d220c04befdcb1d35774853a
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Steps to reproduce:
1. setting `vim.highlight.on_yank`
```
vim.api.nvim_create_autocmd({ "TextYankPost" }, {
pattern = { "*" },
callback = function()
vim.highlight.on_yank({ timeout = 200 })
end,
})
```
2. repeat typing `yeye` ...
3. causes the following error.
```
Error executing vim.schedule lua callback: vim/_editor.lua:0: handle 0x01e96970 is already closing
stack traceback:
[C]: in function 'close'
vim/_editor.lua: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>
```
📝 Test result before fix:
[----------] Global test environment setup.
[----------] Running tests from test/functional/lua/highlight_spec.lua
[ RUN ] vim.highlight.on_yank does not show errors even if buffer is wiped before timeout: 15.07 ms OK
[ RUN ] vim.highlight.on_yank does not show errors even if executed between timeout and clearing highlight: 15.07 ms ERR
test/helpers.lua:73: Expected objects to be the same.
Passed in:
(string) 'Error executing vim.schedule lua callback: vim/_editor.lua:0: handle 0x02025260 is already closing
stack traceback:
[C]: in function 'close'
vim/_editor.lua: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>'
Expected:
(string) ''
|
| | |
|
| |
| |
| |
| |
| | |
Problem: Using uninitialized memory when using 'listchars'.
Solution: Use the length returned by mb_char2bytes(). (closes vim/vim#10576)
https://github.com/vim/vim/commit/74ac29cecd56457ee93f3f71b31b7a2e6d9712d6
|
| | |
|
| |
| |
| |
| | |
Update runtime files
https://github.com/vim/vim/commit/8c1b8cb2e0b52d0853f85c2096a2f22dbc57a788
|
| |
| |
| |
| | |
After the first separator is typed v:errmsg can be set.
Check for its value before typing the first separator.
|
| |
| |
| |
| |
| |
| |
| | |
docs: fix typos and similarly insignificant changes
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
Co-authored-by: smjonas <jonas.strittmatter@gmx.de>
Co-authored-by: kanreki <32443233+kanreki@users.noreply.github.com>
|
| |\
| | |
| | | |
vim-patch:8.2.{1897,1898,5088}
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Value of cmod_verbose is a bit complicated to use.
Solution: Use zero for not set, value + 1 when set. (closes vim/vim#10564)
https://github.com/vim/vim/commit/cd7496382efc9e6748326c6cda7f01003fa07063
Omit has_cmdmod(): only used for Vim9 script
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Command modifier parsing always uses global cmdmod.
Solution: Pass in cmdmod_T to use. Rename struct fields consistently.
https://github.com/vim/vim/commit/e10044015841711b989f9a898d427bcc1fdb4c32
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Command modifiers are saved and set inconsistently.
Solution: Separate parsing and applying command modifiers. Save values in
cmdmod_T.
https://github.com/vim/vim/commit/5661ed6c833e05467cab33cb9b1c535e7e5cc570
Cherry-pick: :0verbose fix from patch 8.2.4741
|
| |\ \
| | |/
| |/| |
perf(memory): use an arena for RPC decoding
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
drawback: tracing memory errors with ASAN is less accurate for arena
allocated memory.
Therefore, to start with it is being used for Object types around
serialization/deserialization exclusively. This is going to have
a large impact especially when TUI is refactored as a co-prosess
as all UI events will be serialized and deserialized by nvim itself.
|
| | |
| | |
| | | |
Work on https://github.com/neovim/neovim/issues/567
|
| | |
| | |
| | |
| | | |
Update runtime files.
https://github.com/vim/vim/commit/6ba83ba9ee292f68aa0b218b3eef42db31c0b632
|
| |/
| |
| |
| | |
`errormsg` is not always set when parsing the command failed (e.g. when
the range contains invalid marks). Check the return value is better.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Not all modifiers supported for :options.
Solution: Use all cmdmod.split flags. (closes vim/vim#4401)
https://github.com/vim/vim/commit/7a1637f4c00ac3d0cbf894803ada1586a1717470
Cherry-pick Test_options_command() change from patch 8.2.0540
|
| |
| |
| | |
This was caught in #18674 since it allows test isolation
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix https://github.com/neovim/neovim/issues/1004
Limitation: All outputs need hit-enter prompt.
Related:
https://github.com/neovim/neovim/pull/6732
https://github.com/neovim/neovim/pull/4382
|
| |\
| | |
| | | |
fix(tests): check for EOF in requests to nvim properly
|
| | | |
|
| |\ \
| | |/
| |/| |
vim-patch:8.2.{5079,5081,5083}
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Autocmd test still fails on MS-Windows.
Solution: Change backward to forward slashes.
https://github.com/vim/vim/commit/db77c49401145d76441fbb3d22a1d7d987681c13
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Autocmd test fails on MS-Windows.
Solution: Set shellslash to get forward slashes.
https://github.com/vim/vim/commit/7c0d0c3c75151e716184397a41ff74ab0429db5a
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: DirChanged autocommand may use freed memory. (Shane-XB Qian)
Solution: Free the memory later. (closes vim/vim#10555)
https://github.com/vim/vim/commit/d8c9d32c8932e93008bfd4e8828ed42f4e9f8315
Code change is N/A as Nvim gets the full current directory again before
applying the autocommand, so this just ports the tests.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem:
lintuncrustify doesn't actually do anything.
Solution:
- Fix the parameters.
- Fail correctly on nonzero result.
followup to #18940
|
| |
| |
| | |
Add a test for what #16537 fixed.
|
| |\
| | |
| | | |
fix(substitute): subtract number of backslashes later
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Substitute test has a one second delay.
Solution: Use ":silent!". Add another test case. (closes vim/vim#10558)
https://github.com/vim/vim/commit/3269efdf014dd3b6e60e330950d40a7cc5d13d3a
|
| | | |
|
| | |
| | |
| | |
| | | |
This is rarely, if ever, used and certainly not tested. It's likely this
isn't functional anymore.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem:
Since 6d57bb89c1ee #18543, luacheck is not found on some systems when
running the "lintlua" target.
Solution:
- Move the find_program() to the top-level CMakeLists.txt
- Define a def_cmd_target() function with fewer assumptions than the old
lint() function.
- Move "lintuncrustify" to src/nvim/CMakeLists.txt so it can reuse the
$LINT_NVIM_SOURCES already defined there.
- Make the lint targets _fatal_ by default. There is little reason for
the "lint" umbrella target defined in Makefile to exist if it's going
to ignore the absence of the actual linters.
- For now, keep the uncrustify call in a separate cmake script so that
it can be silenced (too noisy).
|