summaryrefslogtreecommitdiffstatshomepage
path: root/test/functional/ex_cmds/cmd_map_spec.lua
AgeCommit message (Collapse)AuthorFiles
2026-04-20refactor(test): drop deprecated exc_exec #39242Justin M. Keyes1
2025-05-04feat(messages): cleanup Lua error messagesJustin M. Keyes1
"Error" in error messages is redundant. Just provide the context, don't say "Error ...".
2025-03-14test: do not dedent() in feed() (#32884)zeertzjq1
Most callers of feed() do not expect feed() to dedent. Now use a literal space in tests where it looks better.
2024-11-14fix(tests): needing two calls to setup a screen is cringebfredl1
Before calling "attach" a screen object is just a dummy container for (row, col) values whose purpose is to be sent as part of the "attach" function call anyway. Just create the screen in an attached state directly. Keep the complete (row, col, options) config together. It is still completely valid to later detach and re-attach as needed, including to another session.
2024-04-23test: improve test conventionsdundargoc1
Specifically, functions that are run in the context of the test runner are put in module `test/testutil.lua` while the functions that are run in the context of the test session are put in `test/functional/testnvim.lua`. Closes https://github.com/neovim/neovim/issues/27004.
2024-04-10refactor(test): inject after_each differentlyLewis Russell1
2024-04-08test: improve test conventionsdundargoc1
Work on https://github.com/neovim/neovim/issues/27004.
2024-03-11test: correct order of arguments to eq() (#27816)zeertzjq1
2024-02-15vim-patch:9.1.0106: Visual highlight hard to read with 'termguicolors'zeertzjq1
Problem: Visual highlight hard to read with 'termguicolors' (Maxim Kim) Solution: Set Visual GUI foreground to black (with background=light) and lightgrey (with background=dark) (Maxim Kim) fixes: vim/vim#14024 closes: vim/vim#14025 https://github.com/vim/vim/commit/34e4a05d02a016fe230495be8f6c60ddd56f9567 Co-authored-by: Maxim Kim <habamax@gmail.com>
2024-01-12test: rename (meths, funcs) -> (api, fn)Lewis Russell1
2024-01-03refactor: format test/*Justin M. Keyes1
2023-12-09test: avoid repeated screen lines in expected stateszeertzjq1
This is the command invoked repeatedly to make the changes: :%s/^\(.*\)|\%(\*\(\d\+\)\)\?$\n\1|\%(\*\(\d\+\)\)\?$/\=submatch(1)..'|*'..(max([str2nr(submatch(2)),1])+max([str2nr(submatch(3)),1]))/g
2023-10-10docs: small fixesdundargoc1
Co-authored-by: Wansmer <wansmer@gmail.com> Co-authored-by: Andrew Voynov <andrewvoynov.b@gmail.com> Co-authored-by: David Moberg <david.moberg@mediatek.com>
2023-05-08vim-patch:8.2.3887: E1135 is used for two different errorszeertzjq1
Problem: E1135 is used for two different errors. Solution: Renumber one error. https://github.com/vim/vim/commit/806da5176e9e9ab011d927c4ca33a8dde1769539 Co-authored-by: Bram Moolenaar <Bram@vim.org>
2023-05-08vim-patch:8.2.1978: making a mapping work in all modes is complicatedzeertzjq1
Problem: Making a mapping work in all modes is complicated. Solution: Add the <Cmd> special key. (Yegappan Lakshmanan, closes vim/vim#7282, closes 4784, based on patch by Bjorn Linse) https://github.com/vim/vim/commit/957cf67d50516ba98716f59c9e1cb6412ec1535d Change docs to match Vim if it's wording is better. Change error numbers to match Vim. Co-authored-by: Bram Moolenaar <Bram@vim.org>
2022-05-03test: add more tests for K_SPECIAL escaping in <Cmd> mappingzeertzjq1
2022-04-30test: add test for <Cmd> mapping with character containing K_SPECIAL bytezeertzjq1
2022-04-29feat(mappings): allow special keys and modifiers in <Cmd> mappingzeertzjq1
2022-03-27feat(test): use nvim_exec in helpers.source() #16064Justin M. Keyes1
helpers.source() was a hack to work around the lack of anonymous :source. Its "create tempfile" behavior is not a required part of most tests that use it. Some tests still need the old "create tempfile" behavior either because they test SID behavior, or because of missing nvim_exec features: #16071
2019-01-15screen: don't unconditionally clear messages on window scrollBjörn Linse1
In vim, scrolling a window might mess up the cmdline. To keep it simple, cmdline was always cleared for any window scroll. In nvim, where safe scrolling is implemented in the TUI layer, this problem doesn't exist. Clearing the message on scrolling, when we not do it e.g when switching tabs is a bit weird, as the former is a much smaller context change. A vim patch introduced the possibility to avoid the cmdlline clear for redraws caused by async events. This case will now trivially be covered, as the redraw is always avoided. vim-patch:8.0.0592: if a job writes to a buffer screen is not updated
2018-12-01insert: make <cmd> mapping work in completion (CTRL-X) modeBjörn Linse1
2018-09-13getchar: allow <SID> in <Cmd> mappingBjörn Linse1
2018-08-17cmdline: always use save_cmdline before command_line_enterBjörn Linse1
":normal :" might be invoked in various ways, so its safest to always allow recursive invocation of cmdline mode
2018-03-31msg: do not scroll entire screen (#8088)Björn Linse1
2018-03-23getchar: implement <Cmd> key to invoke command in any modeBjörn Linse1