aboutsummaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
...
* | | | test(old): move some tests from assert_spec.lua to test_assert.vimzeertzjq2022-02-13
|/ / /
* | | feat(api): add strikethrough, nocombine to set_hlChristian Clason2022-02-12
| | |
* | | test: convert some colorcolumn tests to Lua screen testszeertzjq2022-02-12
| | |
* | | Merge pull request #17365 from kevinhwang91/fix-ts-empty-linesChristian Clason2022-02-11
|\ \ \ | | | | | | | | fix(query.lua): check empty table for lines
| * | | fix: append test for checking zero width node rangekevinhwang912022-02-11
| | |/ | |/|
* | | test: convert Test_file_changed_dialog() to Lua functional testzeertzjq2022-02-11
| | |
* | | Merge pull request #17360 from lewis6991/fix-window-closeChristian Clason2022-02-11
|\ \ \ | |/ / |/| | fix: close floating windows when calling win_close()
| * | fix: close floating windows when calling win_close()Rom Grk2022-02-10
| | |
* | | Merge pull request #17012 from EdmundsEcho/fix-checkhealthzeertzjq2022-02-11
|\ \ \ | | | | | | | | prevent checkhealth failure when plugin's check returns void
| * | | fix(healthcheck): handle empty reportsEdmund Cape2022-02-09
| | | |
* | | | fix(api): use changedir_func() in nvim_set_current_dir()zeertzjq2022-02-10
| |/ / |/| | | | | | | | Co-Authored-By: smolck <46855713+smolck@users.noreply.github.com>
* | | vim-patch:8.2.4242: put in Visual mode cannot be repeatedzeertzjq2022-02-09
|/ / | | | | | | | | | | | | | | | | | | Problem: Put in Visual mode cannot be repeated. Solution: Use "P" to put without yanking the deleted text into the unnamed register. (Shougo Matsushita, closes vim/vim#9591) https://github.com/vim/vim/commit/fb55207ed17918c8a2a6cadf5ad9d5fcf686a7ab Cherry-pick get_y_previous() and set_y_previous() from patch 8.1.1736. Nvim has removed y_current, so code related to it is N/A.
* | test: add Lua functional tests for Ex modezeertzjq2022-02-08
| |
* | vim-patch:8.1.0711: test files still use function!zeertzjq2022-02-07
| | | | | | | | | | | | | | | | Problem: Test files still use function!. Solution: Remove the exclamation mark. Fix overwriting a function. https://github.com/vim/vim/commit/1e1153600c0377472d62cc553173fe555ddcf5a7 Some of the changes were already applied previously.
* | Merge pull request #17279 from zeertzjq/state-enter-vpeekcbfredl2022-02-06
|\ \ | | | | | | fix(event-loop): call vpeekc() directly first to check for character
| * | fix(event-loop): call vpeekc() directly first to check for characterzeertzjq2022-02-03
| | | | | | | | | | | | Expand mappings first by calling `vpeekc()` directly.
* | | Merge pull request #17194 from zeertzjq/inccommand-prev-subzeertzjq2022-02-06
|\ \ \ | | | | | | | | fix(inccommand): do not change reg_prev_sub when previewing
| * | | fix(inccommand): do not change reg_prev_sub when previewingzeertzjq2022-01-25
| | | |
* | | | fix(diff): make algorithm work for vim.diff (#17300)Lewis Russell2022-02-05
| | | | | | | | | | | | Fixes #17207
* | | | fix(--headless): do not block on press-enter prompts when no UIglacambre2022-02-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit fixes #9358, where emitting multiple messages with 'echo' or a single one with 'echom' or 'echoerr' would result in a press-enter prompt that couldn't be dismissed by pressing enter. This requires adapting a few tests to spawn a UI before testing whether press-enter prompts are blocking. It also fixes #11718, as when combined with #15910 it enables making sure that neovim never blocks and emits messages on startup.
* | | | test(old): add test_expand.vimzeertzjq2022-02-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes expand_spec.lua and copies test_expand.vim from Vim at version v8.1.2278. The rest of patch 8.1.2278 were already applied in #15952, so this marks that patch as fully ported. vim-patch:8.1.2278: using "cd" with "exe" may fail Problem: Using "cd" with "exe" may fail. Solution: Use chdir() instead. https://github.com/vim/vim/commit/3503d7c94a6c8c2a5ca1665d648d0cb81afcc863
* | | | vim-patch:8.2.1128: the write message mentions characters, but it's byteszeertzjq2022-02-04
| | | | | | | | | | | | | | | | | | | | | | | | Problem: The write message mentions characters, but it's actually bytes. Solution: Change "C" to "B" and "characters" to "bytes". https://github.com/vim/vim/commit/3f40ce78f5c178d15871bd784ed878c78f0b8a44
* | | | test: convert some search stat screendump tests to Lua screen testszeertzjq2022-02-04
| | | |
* | | | ci: only show last 100 lines of log on errorDundar Göc2022-02-03
| | | |
* | | | fix(api/nvim_win_call): share common win_execute logicSean Dewar2022-02-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have to be sure that the bugs fixed in the previous patches also apply to nvim_win_call. Checking v8.1.2124 and v8.2.4026 is especially important as these patches were only applied to win_execute, but nvim_win_call is also affected by the same bugs. A lot of win_execute's logic can be shared with nvim_win_call, so factor it out into a common macro to reduce the possibility of this happening again.
* | | | vim-patch:8.2.4028: ml_get error with :doautoall and Visual areaSean Dewar2022-02-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: ml_get error with :doautoall and Visual area. (Sean Dewar) Solution: Disable Visual mode while executing autocommands. https://github.com/vim/vim/commit/cb1956d6f2aece8ad93e19e5d4c7e0b5e405f056 This should also fix #16937 for nvim_buf_call, so test for it.
* | | | fix(health): do not run external processes in a shellzeertzjq2022-02-03
| |/ / |/| |
* | | Merge pull request #17187 from lewis6991/masterbfredl2022-02-01
|\ \ \ | | | | | | | | feat(highlight): ns=0 to set :highlight namespace
| * | | feat(highlight): ns=0 to set :highlight namespaceLewis Russell2022-02-01
| | | | | | | | | | | | | | | | Passing ns=0 to nvim_set_hl will alter the `:highlight` namespace.
* | | | Merge pull request #17113 from zeertzjq/vim-8.2.2569zeertzjq2022-02-01
|\ \ \ \ | |/ / / |/| | | feat(statusline): support multibyte fillchar
| * | | feat(statusline): support multibyte fillcharzeertzjq2022-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This includes a partial port of Vim patch 8.2.2569 and some changes to nvim_eval_statusline() to allow a multibyte fillchar. Literally every line of C code touched by that patch has been refactored in Nvim, and that patch contains some irrelevant foldcolumn tests I'm not sure how to port (as Nvim's foldcolumn behavior has diverged from Vim's).
* | | | Merge pull request #17254 from zeertzjq/vim-8.2.3787zeertzjq2022-02-01
|\ \ \ \ | | | | | | | | | | vim-patch:8.2.{3787,3932,3934,3935,3938}: text formatting patches
| * | | | test: remove 003_cindent_spec.luazeertzjq2022-01-31
| | | | | | | | | | | | | | | | | | | | This no longer needed as Vim patch 8.1.1434 has been ported.
* | | | | [RFC] fix: has('python') error (#17252)Shougo2022-01-31
|/ / / / | | | | | | | | | | | | | | | | * fix: has('python') error * fix: functional tests
* | | | chore: typo fixes (#16921)dundargoc2022-01-29
| | | | | | | | | | | | Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* | | | vim-patch:8.2.3917: the eval.txt help file is way too bigDaniel Steinberg2022-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The eval.txt help file is way too big. Solution: Move the builtin function details to a separate file. https://github.com/vim/vim/commit/1cae5a0a034d0545360387407a7a409310f1efe2 Note: Neovim-specific references to |functions| were changed to |builtin-functions|. This included updates to: 1. test/functional/vimscript/functions_spec.lua 2. test/functional/vimscript/eval_spec.lua 3. runtime/doc/lua.txt
* | | | Merge pull request #17222 from bfredl/babajpy2bfredl2022-01-29
|\ \ \ \ | | | | | | | | | | feat(provider)!: remove support for python2 and python3.[3-6]
| * | | | feat(provider)!: remove support for python2 and python3.[3-5]Björn Linse2022-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These versions of python has reached End-of-life. getting rid of python2 support removes a lot of logic to support two incompatible python versions in the same version.
* | | | | Merge pull request #17192 from zeertzjq/aucmd-redrawingdisabledbfredl2022-01-29
|\ \ \ \ \ | |/ / / / |/| | | | fix: set RedrawingDisabled before entering aucmd_win
| * | | | fix: set RedrawingDisabled before entering aucmd_winzeertzjq2022-01-25
| | |/ / | |/| |
* | | | vim-patch:8.2.4090: after restoring a session buffer order can be quite ↵Evgeni Chasnovski2022-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | different (#17112) Problem: After restoring a session buffer order can be quite different. Solution: Create buffers first. (Evgeni Chasnovski, closes vim/vim#9520) https://github.com/vim/vim/commit/26ebf1f036517ebeacf571c333a83cca7e13bbe2 --------------- As in Vim, this basically reverts 8.1.0829 providing different solution (see vim/vim#9520). Regarding Neovim, this basically reverts changes from #15062. Test about restoring same terminals was a bit too restrictive with using actual buffer ids, which changed with this patch (now they should be in the same order as at `mksession` call), so I tweaked it.
* | | | Merge pull request #17209 from bb010g/patch-1bfredl2022-01-29
|\ \ \ \ | | | | | | | | | | fix(eval): v:lua support for `-` in module names
| * | | | fix(eval): v:lua support for `-` in module namesbb010g2022-01-28
| | | | |
* | | | | fix(input): remove reinterpreted ALT/META chords from recorded macrozeertzjq2022-01-29
|/ / / /
* | | | Merge pull request #17183 from notomo/expose-extmark-right-gravitybfredl2022-01-28
|\ \ \ \ | | | | | | | | | | feat(api): expose extmark right_gravity and end_right_gravity
| * | | | feat(api): expose extmark right_gravity and end_right_gravitynotomo2022-01-24
| | | | |
* | | | | fix(completion): update submode message when selecting from API (#17022)zeertzjq2022-01-28
| | | | |
* | | | | Merge pull request #17175 from zeertzjq/vim-8.2.3095bfredl2022-01-27
|\ \ \ \ \ | | | | | | | | | | | | vim-patch:8.2.3095: with 'virtualedit' set to "block" block selection is wrong
| * | | | | vim-patch:8.2.3095: with 'virtualedit' set to "block" block selection is wrongzeertzjq2022-01-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: With 'virtualedit' set to "block" block selection is wrong after using "$". (Marco Trosi) Solution: Compute the longest selected line. (closes vim/vim#8495) https://github.com/vim/vim/commit/b17ab86e7b8712206aa9ea7198c28db969e25936
* | | | | | fix(ts): escape lang when loading parsers (#16668)Lewis Russell2022-01-27
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When trying to load a language parser, escape the value of the language. With language injection, the language might be picked up from the buffer. If this value is erroneous it can cause `nvim_get_runtime_file` to hard error. E.g., the markdown expression `~~~{` will extract '{' as a language and then try to get the parser using `parser/{*` as the pattern.
generated by cgit (git 2.34.1) at 2025-06-25 02:54:11 +0000