aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/testdir
Commit message (Collapse)AuthorAge
...
* tests: fix Test_help_tagjump()Marco Hinz2019-01-17
| | | | | | | | | | | | | | | | | | | The Vim version of Test_help_tagjump() tests for `:help sm?le` here. That command got removed from Nvim, so the test was changed to check against `:help sp?it` instead. The new test already handled the case that on Win `:h split` would jump to the entry for split() and on all other systems to the entry for :split. Then this commit happened: bb3aa824b lua/stdlib: vim.inspect, string functions Since then `:h split` would jump to split() for macOS as well! I'm not sure why. Anyway, instead of adding another check for has('mac'), we change the test once more to be more akin to the original test. Instead of testing for :smile, which is exclusive to Vim, we check against :checkhealth, which is exclusive to Nvim.
* vim-patch:8.1.0449: fix display of 'rnu' with folded lines #9481Michael Vilim2019-01-11
| | | | | | | | | | | | | | | | | | | | | | | | Problem: When 'rnu' is set folded lines are not displayed correctly. (Vitaly Yashin) Solution: When only redrawing line numbers do draw folded lines. (closes vim/vim#3484) https://github.com/vim/vim/commit/7701f308565fdc7b5096a6597d9c3b63de0bbcec --- Explanation: Before this patch, relative line numbers would update on a cursor movement and overwrite fold highlighting in the line number columns. Other operations can cause the fold highlighting to overwrite the line number styles. Together, this causes the highlighting in the line number columns to flicker back and forth while editing. Test case: create `t.vim` with these contents: set fdm=marker rnu foldcolumn=2 call setline(1, ["{{{1", "nline 1", "{{{1", "line 2"]) and then call `nvim -u NORC -S t.vim` and press `j`; observe that the fold highlighting disappears.
* vim-patch:8.1.0648: custom operators can't act upon forced motionPedro L. Ramos2019-01-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Custom operators can't act upon a forced motion. (Christian Wellenbrock) Solution: Add the forced motion to the mode() result. (Christian Brabandt, closes vim/vim#3490) https://github.com/vim/vim/commit/5976f8ff00efcb3e155a89346e44f2ad43d2405a closes #8667 closes #9476 Christian Wellenbrock: > For (most) built in text objects it's possible to force operation on > them to be linewise, for example by using `dVab` (`:h o_V`, > `motion_force`). When using custom text objects (defined as mappings > by plugins for example), this doesn't currently work. > > Example: > > onoremap x viw > > Open a file with a few lines each containing some words. With the > cursor on any word, try: > > 1. `dw` (builtin) deletes some characters > 2. `dVw` (builtin) deletes linewise > 3. `dx` (from mapping) deletes some characters > 4. `dVx` (from mapping) deletes some characters, but should delete > linewise ref: https://github.com/wellle/targets.vim/issues/214 ref: https://gitter.im/neovim/neovim?at=5b379ff7f1664406610e7483
* vim-patch:8.1.0696: when test_edit fails 'insertmode' may not be resetJan Edmund Lazo2019-01-06
| | | | | | | | | Problem: When test_edit fails 'insertmode' may not be reset and the next test may get stuck. (James McCoy) Solution: Always reset 'insertmode' after executing a test. Avoid that an InsertCharPre autocommand or a 'complete' function can change the state. (closes vim/vim#3768) https://github.com/vim/vim/commit/8ad16da7290190f55f88073d5586dfe133fddf45
* vim-patch:8.1.0687: sentence text object in Visual mode is not testedJan Edmund Lazo2019-01-05
| | | | | | Problem: Sentence text object in Visual mode is not tested. Solution: Add a test. (Dominique Pelle, closes vim/vim#3758) https://github.com/vim/vim/commit/6d3a1940be9d3f2b079f81baa9b19f839289b69e
* vim-patch:8.1.0653: arglist test fails on MS-windowsJan Edmund Lazo2019-01-03
| | | | | | Problem: Arglist test fails on MS-windows. Solution: Only use a file name with a double quote on Unix. https://github.com/vim/vim/commit/3de8c2d1f027410db6a06f0fcd3355d96c8b8596
* vim-patch:8.1.0651: :args \"foo works like :args without argumentJan Edmund Lazo2019-01-03
| | | | | | Problem: :args \"foo works like :args without argument. Solution: Fix check for empty argument. (closes vim/vim#3728) https://github.com/vim/vim/commit/2ac372ccee1af6f9fa105bf2648d5e4efa554236
* vim-patch:8.0.0251: not easy to select Python 2 or 3 (#9173)David Jimenez2019-01-02
| | | | | | Problem: It is not so easy to write a script that works with both Python 2 and Python 3, even when the Python code works with both. Solution: Add 'pyxversion', :pyx, etc. (Marc Weber, Ken Takata) https://github.com/vim/vim/commit/f42dd3c3901ea0ba38e67a616aea9953cae81b8d
* vim-patch:8.1.0627: Python cannot handle function name of script-local ↵Jan Edmund Lazo2018-12-23
| | | | | | | | function (#9392) Problem: Python cannot handle function name of script-local function. Solution: Use <SNR> instead of the special byte code. (Ozaki Kiichi, closes vim/vim#3681) https://github.com/vim/vim/commit/9123c0b31a283f460ed2b6af95080120cf528118
* vim-patch:8.1.0596: not all parts of printf() are testedJan Edmund Lazo2018-12-16
| | | | | | Problem: Not all parts of printf() are tested. Solution: Add a few more test cases. (Dominique Pelle, closes vim/vim#3691) https://github.com/vim/vim/commit/21e551cce26ea6ff389b6c90f1945facf1a8a066
* vim-patch:8.1.0588: cannot define a sign with space in the textJan Edmund Lazo2018-12-14
| | | | | | Problem: Cannot define a sign with space in the text. Solution: Allow for escaping characters. (Ben Jackson, closes vim/vim#2967) https://github.com/vim/vim/commit/06b056e110005ce0dd97b8c6333405afd06c36fc
* vim-patch:8.1.0585: undo test may fail on MS-WindowsJan Edmund Lazo2018-12-14
| | | | | | Problem: Undo test may fail on MS-Windows. Solution: Also handle lower case drive letters. https://github.com/vim/vim/commit/56242f2b08737677812513c447955579a19aa620
* vim-patch:8.0.1748: CmdlineEnter command uses backslash instead of slashJan Edmund Lazo2018-12-12
| | | | | | Problem: CmdlineEnter command uses backslash instead of slash. Solution: Don't treat the character as a file name. (closes vim/vim#2837) https://github.com/vim/vim/commit/a4baf5b32519855bb176a7aa0e9397c137ca890a
* vim-patch:8.0.1445: cannot act on edits in the command lineBjörn Linse2018-12-12
| | | | | | | | Problem: Cannot act on edits in the command line. Solution: Add the CmdlineChanged autocommand event. (xtal8, closes vim/vim#2603, closes vim/vim#2524) https://github.com/vim/vim/commit/153b704e20f9c269450a7d3ea8cafcf942579ab7
* vim-patch:8.1.0574: 'commentstring', fold marker in C (#9339)Jan Edmund Lazo2018-12-10
| | | | | | Problem: 'commentstring' not used when adding fold marker in C. Solution: Require white space before middle comment part. (mostly by Hirohito Higashi) https://github.com/vim/vim/commit/4af7259b2b35e85c590d54908fcd248d2c733be8
* vim-patch:8.1.0497: :%diffput changes order of linesAnatolii Sakhnik2018-12-09
| | | | | | | Problem: :%diffput changes order of lines. (Markus Braun) Solution: Do adjust marks when using internal diff. https://github.com/vim/vim/commit/5f57bdcab77bc417ae0357fe8ad6c7259b6d25df
* vim-patch:8.1.0458: ml_get error and crash when using "do"Anatolii Sakhnik2018-12-09
| | | | | | | | Problem: Ml_get error and crash when using "do". Solution: Adjust cursor position also when diffupdate is not needed. (Hirohito Higashi) https://github.com/vim/vim/commit/df77cef92ec034796723ffa3adb12e8b46daa98e
* vim-patch:8.1.0397: no event triggered after updating diffsAnatolii Sakhnik2018-12-09
| | | | | | | Problem: No event triggered after updating diffs. Solution: Add the DiffUpdated event. https://github.com/vim/vim/commit/e8fa05b5bc2d6d76bf5af50176a63655d00d1110
* vim-patch:8.1.0375: cannot use diff mode with Cygwin diff.exeAnatolii Sakhnik2018-12-09
| | | | | | | Problem: Cannot use diff mode with Cygwin diff.exe. (Igor Forca) Solution: Skip over unrecognized lines in the diff output. https://github.com/vim/vim/commit/3b8defd0a52fc1276816608e7bb24b628ab14c2e
* vim-patch:8.1.0360: using an external diff program is slow and inflexibleAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | Problem: Using an external diff program is slow and inflexible. Solution: Include the xdiff library. (Christian Brabandt) Use it by default. https://github.com/vim/vim/commit/e828b7621cf9065a3582be0c4dd1e0e846e335bf vim-patch:8.1.0360 vim-patch:8.1.0364 vim-patch:8.1.0366 vim-patch:8.1.0370 vim-patch:8.1.0377 vim-patch:8.1.0378 vim-patch:8.1.0381 vim-patch:8.1.0396 vim-patch:8.1.0432
* vim-patch:8.1.0570: 'commentstring' not used when adding fold marker (#9331)Jan Edmund Lazo2018-12-08
| | | | | | Problem: 'commentstring' not used when adding fold marker. (Maxim Kim) Solution: Only use empty 'comments' middle when leader is empty. (Christian Brabandt, closes vim/vim#3670) https://github.com/vim/vim/commit/539328197c51c1586cbbb6b6be3db3c412249b49
* vim-patch:8.1.0564: setting v:errors to wrong type still possibleJan Edmund Lazo2018-12-06
| | | | | | Problem: Setting v:errors to wrong type still possible. Solution: Return after giving an error message. (Christian Brabandt) https://github.com/vim/vim/commit/88b53fd0521d1e62df17a8a1f2181425e9d4854c
* vim-patch:8.0.1425: execute() does not work in completion of user command ↵Jan Edmund Lazo2018-12-06
| | | | | | | (#9317) Problem: execute() does not work in completion of user command. (thinca) Solution: Switch off redir_off and restore it. (Ozaki Kiichi, closes vim/vim#2492) https://github.com/vim/vim/commit/2095148277cf1c4e7b3bbaf4e34812b7cfe3011b
* vim-patch:8.1.0559: command line completion not sufficiently testedJan Edmund Lazo2018-12-03
| | | | | | Problem: Command line completion not sufficiently tested. Solution: Add more tests. (Dominique Pelle, closes vim/vim#3622) https://github.com/vim/vim/commit/b513d3079bbe3f59a1f1a3d6931939a76cd7e54a
* vim-patch:8.1.0553: it is not easy to edit a script that was sourced (#9298)Jan Edmund Lazo2018-12-01
| | | | | | Problem: It is not easy to edit a script that was sourced. Solution: Add a count to ":scriptnames", so that ":script 40" edits the script with script ID 40. https://github.com/vim/vim/commit/07dc18ffa4e7ed202f219fe2fd3d6f58246f71f9
* test/macOS: adjust time-sensitive testsJustin M. Keyes2018-11-30
| | | | | | | | | | | | | | | | | | | | From test_timers.vim: Found errors in Test_paused(): First run: function RunTheTest[35]..Test_paused line 20: Expected range 0 - 100, but got 123 Second run: function RunTheTest[35]..Test_paused line 20: Expected range 0 - 100, but got 106 previously: #9220 - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms.
* test: adjust time-sensitive testsJustin M. Keyes2018-11-30
| | | | | | | | | | | | | | | | | | | | | From test_alot.vim: Found errors in Test_lambda_with_timer(): First run: function RunTheTest[35]..Test_lambda_with_timer line 19: Expected True but got 0 Second run: function RunTheTest[35]..Test_lambda_with_timer line 19: Expected True but got 0 previously: #9220 - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms. - Call test_garbagecollect_now(), as Vim does.
* vim-patch:8.1.0098: segfault when pattern with \z() is very slow (#9283)Justin M. Keyes2018-11-29
| | | | | | | | Problem: Segfault when pattern with \z() is very slow. Solution: Check for NULL regprog. Add "nfa_fail" to test_override() to be able to test this. Fix that 'searchhl' resets called_emsg. https://github.com/vim/vim/commit/bcf9442307075bac40d44328c8bf7ea21857b138 closes #8788
* vim-patch:8.1.0038: popup test causes Vim to exitJan Edmund Lazo2018-11-20
| | | | | | Problem: Popup test causes Vim to exit. Solution: Disable the broken part of the test for now. https://github.com/vim/vim/commit/680c99b2efc7e2a9e6b3d611133f43fb7f8c6811
* vim-patch:8.0.1731: characters deleted on completionJan Edmund Lazo2018-11-20
| | | | | | | Problem: Characters deleted on completion. (Adrià Farrés) Solution: Also check the last item for the ORIGINAL_TEXT flag. (Christian Brabandt, closes vim/vim#1645) https://github.com/vim/vim/commit/e87edf3b85f607632e5431640071fdbc36b685b2
* vim-patch:8.0.1171: popup test is still a bit flakyJan Edmund Lazo2018-11-19
| | | | | | Problem: Popup test is still a bit flaky. Solution: Change term_wait() calls. (Ozaki Kiichi) https://github.com/vim/vim/commit/712549e04eddd6687c4b7654ec9af6da6c365603
* vim-patch:8.0.1165: popup test is still flakyJan Edmund Lazo2018-11-19
| | | | | | Problem: Popup test is still flaky. Solution: Add a term_wait() call. (Ozaki Kiichi) https://github.com/vim/vim/commit/f52c38315669f85bbcf3bd74c590148bf588f6c6
* vim-patch:8.0.1163: popup test is flakyJan Edmund Lazo2018-11-19
| | | | | | Problem: Popup test is flaky. Solution: Add a WaitFor() and fix another. https://github.com/vim/vim/commit/c79977a437d91306d576fb59e490601409503303
* vim-patch:8.0.1249: no error when WaitFor() gets an invalid wrong expressionJan Edmund Lazo2018-11-19
| | | | | | | Problem: No error when WaitFor() gets an invalid wrong expression. Solution: Do not ignore errors in evaluationg the expression. Fix places where the expression was wrong. https://github.com/vim/vim/commit/c20e0d52071a3f6e12321ec3344024faa4695da9
* vim-patch:8.0.0737: crash when X11 selection is very bigJan Edmund Lazo2018-11-19
| | | | | | | Problem: Crash when X11 selection is very big. Solution: Use static items instead of allocating them. Add callbacks. (Ozaki Kiichi) https://github.com/vim/vim/commit/cdb7e1b7f9e18a7b165ff09103a9994f84966123
* vim-patch:8.0.1427: the :leftabove modifier doesn't work for :copenJan Edmund Lazo2018-11-19
| | | | | | Problem: The :leftabove modifier doesn't work for :copen. Solution: Respect the split modifier. (Yegappan Lakshmanan, closes vim/vim#2496) https://github.com/vim/vim/commit/de04654ddc865af94ef04b1738b335a924be7923
* vim-patch:8.1.0398: no test for -o and -O command line arguments (#9253)Jan Edmund Lazo2018-11-19
| | | | | Problem: No test for -o and -O command line arguments. Solution: Add a test. (Dominique Pelle, closes vim/vim#3438) https://github.com/vim/vim/commit/8f4499b81612568b4964e8445d86e34e6d644b13
* vim-patch:8.1.0536: file time test fails when using NFS (#9251)James McCoy2018-11-18
| | | | | | Problem: File time test fails when using NFS. Solution: Use three file times instead of localtim(). (James McCoy, closes vim/vim#3618) https://github.com/vim/vim/commit/addc156c38d442367854f71baee31f2eb003c699
* vim-patch:8.1.0318: the getftype() test may fail for char devicesJan Edmund Lazo2018-11-17
| | | | | | | Problem: The getftype() test may fail for char devices if the file disappeared in between the listing and the getftype() call. Solution: Ignore empty result. (Ozaki Kiichi, closes vim/vim#3360) https://github.com/vim/vim/commit/3b3a506f57a397d83db361be35189c591bff10fb
* vim-patch:8.1.0299: misplaced commentJan Edmund Lazo2018-11-17
| | | | | | Problem: misplaced comment Solution: Remove comment https://github.com/vim/vim/commit/142ae736d984f4575c1c6ec1a4f679ae4ddf9413
* vim-patch:8.1.0298: window resize test sometimes fails on MacJan Edmund Lazo2018-11-17
| | | | | | Problem: Window resize test sometimes fails on Mac. Solution: Add Test_popup_and_window_resize() to flaky tests. https://github.com/vim/vim/commit/46fad2ef0bd5124f1be22c807214c243fb5611d8
* vim-patch:8.1.0258: not enough testing for the CompleteDone eventJan Edmund Lazo2018-11-17
| | | | | | Problem: Not enough testing for the CompleteDone event. Solution: Add a test. (closes vim/vim#3297) https://github.com/vim/vim/commit/af559d2c9f44bc88a7d94f9236b3c024563a8e73
* vim-patch:8.1.0146: when $LANG is set the compiler test may fail (#9238)Jan Edmund Lazo2018-11-15
| | | | | Problem: When $LANG is set the compiler test may fail. Solution: Unset $LANG. https://github.com/vim/vim/commit/f0447e89a52885630947510f2d1b55f665a1a20e
* oldtests: skip Test_spellinfo()Jan Edmund Lazo2018-11-12
| | | | nvim supports only `set encoding=utf8`.
* vim-patch:8.1.0340: no test for :spellinfoJan Edmund Lazo2018-11-12
| | | | | | Problem: No test for :spellinfo. Solution: Add a test. (Dominique Pelle, closes vim/vim#3394) https://github.com/vim/vim/commit/9049b686121367941bf534c041975938135c7e20
* vim-patch:8.1.0516: :move command sets 'modified' #9224Jan Edmund Lazo2018-11-11
| | | | | Problem: :move command marks buffer modified when nothing changed. Solution: Do not set 'modified'. Add a test. (Jason Franklin) https://github.com/vim/vim/commit/ddd1f9183bed00d096f29c503721ac559174a29f
* test: adjust time-sensitive tests (#9220)Justin M. Keyes2018-11-10
| | | | | | | | | | | | | - window_split_tab_spec.lua: Put cursor at bottom of :terminal buffer so that it follows output. - inccommand_spec.lua: Increase timeout to allow 2nd retry. - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms.
* vim-patch:8.1.0337: :file fails in quickfix command (#9215)Jan Edmund Lazo2018-11-09
| | | | | | Problem: :file fails in quickfix command. Solution: Allow :file without argument when curbuf_lock is set. (Jason Franklin) https://github.com/vim/vim/commit/379fb76b080521f7c09265ec3264b9e698923518
* vim-patch:8.1.0511: ml_get error when calling a function with a range (#9207)Jan Edmund Lazo2018-11-06
| | | | | Problem: ml_get error when calling a function with a range. Solution: Don't position the cursor after the last line. https://github.com/vim/vim/commit/9e353b5265bd7fa103caf4e5a9b3c99f344f548e
* test/timer_spec: relax lower-boundJustin M. Keyes2018-11-05
| | | | | | | | | | | | | Test is unreliable on macOS 10.13. The lower-bound isn't central to the purpose of the test, so just relax it. ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms. related: #6829
generated by cgit (git 2.34.1) at 2026-02-20 03:57:07 +0000