aboutsummaryrefslogtreecommitdiff
path: root/test/functional/legacy
Commit message (Collapse)AuthorAge
...
* vim-patch:8.1.0295: no 'incsearch' highlighting for :vimgrep and similarAufar Gilbran2020-09-11
| | | | | | | Problem: No 'incsearch' highlighting for :vimgrep and similar commands. Solution: Parse the :vimgrep command and similar ones to locate the search pattern. (Hirohito Higashi, closes vim/vim#3344) https://github.com/vim/vim/commit/264cf5cfaf40e704aea2578e70c15ed9a9d0161e
* vim-patch:8.1.0291: 'incsearch' highlighting not used for :sortAufar Gilbran2020-09-11
| | | | | | Problem: 'incsearch' highlighting not used for :sort. Solution: Handle pattern in :sort command. https://github.com/vim/vim/commit/81f56536b1bc324eb173924a8cf4d7dbbf4f3fdb
* vim-patch:8.2.1472: ":argdel" does not work like ":.argdel" as documentedJan Edmund Lazo2020-08-17
| | | | | | | | Problem: ":argdel" does not work like ":.argdel" as documented. (Alexey Demin) Solution: Make ":argdel" work like ":.argdel". (closes vim/vim#6727) Also fix giving the error "0 more files to edit". https://github.com/vim/vim/commit/7b22117c4ecf383b6f35acef041773a83ec28220
* vim-patch:8.2.0072: memory test still fails on Cirrus CIJan Edmund Lazo2020-08-02
| | | | | | | | | | | | | | | | | | | | | | | Problem: Memory test still fails on Cirrus CI. Solution: Allow for a tiny bit more tolerance in the upper limit. https://github.com/vim/vim/commit/bb062c1588c324a1ce4cf01fd5e0780e83aaabe4 Check memory usage after Neovim sourced the Vimscript files. https://github.com/neovim/neovim/pull/12679 N/A patches for version.c: vim-patch:8.2.0062: memory test is flaky on FreeBSD Problem: Memory test is flaky on FreeBSD. Solution: Add a short sleep before getting the first size. https://github.com/vim/vim/commit/e7538ae997b3983d0c91a886a74ebacedd752164 vim-patch:8.2.0071: memory test often fails on Cirrus CI Problem: Memory test often fails on Cirrus CI. Solution: Allow for more tolerance in the upper limit. Remove sleep. https://github.com/vim/vim/commit/1832d12aea30f1533f3c461d9e1530d10f66b162
* vim-patch:8.2.0539: comparing two NULL list failsJan Edmund Lazo2020-07-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Comparing two NULL list fails. Solution: Change the order of comparing two lists. https://github.com/vim/vim/commit/7b293c730b07d1586688e622b8d9cbbb4a52379b N/A patches for version.c: vim-patch:8.2.1187: terminal2 test sometimes hangs in the GUI on Travis Problem: Terminal2 test sometimes hangs in the GUI on Travis. Solution: Disable Test_zz2_terminal_guioptions_bang() for now. https://github.com/vim/vim/commit/c85156bb897085d7f5a8e4e180287f87bf19b948 vim-patch:8.2.1188: memory leak with invalid json input Problem: Memory leak with invalid json input. Solution: Free all keys at the end. (Dominique Pellé, closes vim/vim#6443, closes vim/vim#6442) https://github.com/vim/vim/commit/6d3a7213f58da834b0fc869d05f87e86010c66cf vim-patch:8.2.1196: build failure with normal features Problem: Build failure with normal features. Solution: Add #ifdef. https://github.com/vim/vim/commit/83e7450053399942e1c9efa802c568b51d948541 vim-patch:8.2.1198: terminal2 test sometimes hangs in the GUI on Travis Problem: Terminal2 test sometimes hangs in the GUI on Travis. Solution: Move test function to terminal3 to see if the problem moves too. https://github.com/vim/vim/commit/a4b442614c5ca4ebf32acf5cf0b7b718496f1c94
* vim-patch:8.1.0819: a failed assert with a long string is hard to readJan Edmund Lazo2020-07-19
| | | | | | Problem: A failed assert with a long string is hard to read. Solution: Shorten the assert message. https://github.com/vim/vim/commit/865767126e97d9ac65e052a657b29bbc32dcb512
* vim-patch:8.2.0491: cannot recognize a <script> mapping using maparg()Jan Edmund Lazo2020-06-04
| | | | | | Problem: Cannot recognize a <script> mapping using maparg(). Solution: Add the "script" key. (closes vim/vim#5873) https://github.com/vim/vim/commit/2da0f0c445da3c9b35b2a0cd595d10e81ad2a6f9
* vim-patch:8.1.1435: memory usage test is a bit too flakyerw72020-05-07
| | | | | | Problem: Memory usage test is a bit too flaky. Solution: Adjust the tolerances a bit. (Christian Brabandt) https://github.com/vim/vim/commit/5d508dd39e810d446f29dfd4f4e745b802875001
* vim-patch:8.1.1058: memory usage test may still fail on some systemserw72020-05-07
| | | | | | Problem: Memory usage test may still fail on some systems. Solution: Use 98% of the lower limit. (Christian Brabandt) https://github.com/vim/vim/commit/3a731ee0c2dd34792c1b21fc4c699a84129f1b86
* vim-patch:8.1.1037: memory usage test may still fail on some systemserw72020-05-07
| | | | | | Problem: Memory usage test may still fail on some systems. Solution: Increase tolerance from 3% to 20%. https://github.com/vim/vim/commit/6b6f7aae4a3329d685e512699287605540257b40
* vim-patch:8.1.1033: memory usage test may still fail on some systemserw72020-05-07
| | | | | | | Problem: Memory usage test may still fail on some systems. (Elimar Riesebieter) Solution: Increase tolerance from 1% to 3%. https://github.com/vim/vim/commit/ba64ba093520e85d6bed2595960edb693bdb4c51
* vim-patch:8.1.1031: memory usage test may still failerw72020-05-07
| | | | | | Problem: Memory usage test may still fail. Solution: Drop the unused min value. (Christian Brabandt) https://github.com/vim/vim/commit/f7e47af7760fe054cb645dac9a1e96b23c85804d
* vim-patch:8.1.1027: memory usage test sometimes failserw72020-05-07
| | | | | | Problem: Memory usage test sometimes fails. Solution: Use 80% of before.last as the lower limit. (Christian Brabandt) https://github.com/vim/vim/commit/08cda65ddfbb4bce8cef43726a0c00817fc47327
* vim-patch:8.1.1007: using closure may consume a lot of memoryerw72020-05-07
| | | | | | | Problem: Using closure may consume a lot of memory. Solution: unreference items that are no longer needed. Add a test. (Ozaki Kiichi, closes vim/vim#3961) https://github.com/vim/vim/commit/209b8e3e3bf7a4a3d102134124120f6c7f57d560
* vim-patch:8.1.1510: a plugin cannot easily expand a command like done internallyJan Edmund Lazo2020-03-01
| | | | | | Problem: A plugin cannot easily expand a command like done internally. Solution: Add the expandcmd() function. (Yegappan Lakshmanan, closes vim/vim#4514) https://github.com/vim/vim/commit/80dad48c5095d30873a42ec82628bdb213125d8e
* vim-patch:8.1.0092: prompt buffer test failserw72020-02-12
| | | | | | | Problem: Prompt buffer test fails. Solution: Set 'nomodified' before closing the window. (Ozaki Kiichi, closes vim/vim#3051 https://github.com/vim/vim/commit/71ef1ba5e996f34d3e0acbe1d89c4c6bfa5e98ba
* vim-patch:8.1.0036: not restoring Insert mode if leaving prompt buffer with ↵erw72020-02-12
| | | | | | | | | | mouse Problem: Not restoring Insert mode if leaving a prompt buffer by using a mouse click. Solution: Set b_prompt_insert appropriately. Also correct cursor position when moving cursor to last line. https://github.com/vim/vim/commit/891e1fd894720d0b99a9daefa41e8181844f819a
* vim-patch:8.1.0032: BS in prompt buffer starts new lineerw72020-02-12
| | | | | | | Problem: BS in prompt buffer starts new line. Solution: Do not allows BS over the prompt. Make term_sendkeys() handle special keys. Add a test. https://github.com/vim/vim/commit/6b810d92a9cd9378ab46ea0db07079cb789f9faa
* vim-patch:8.1.0027: difficult to make a plugin that feeds a line to a joberw72020-02-12
| | | | | | Problem: Difficult to make a plugin that feeds a line to a job. Solution: Add the nitial code for the "prompt" buftype. https://github.com/vim/vim/commit/f273245f6433d5d43a5671306b520a3230c35787
* doc: fix typos [ci skip] #11787Hye Sung Jung2020-01-30
|
* vim-patch:8.1.1143: may pass weird strings to file name expansionJan Edmund Lazo2020-01-26
| | | | | | Problem: May pass weird strings to file name expansion. Solution: Check for matching characters. Disallow control characters. https://github.com/vim/vim/commit/8f130eda4747e4a4d68353cdb650f359fd01469b
* vim-patch:8.2.0010: test64 is old styleJan Edmund Lazo2019-12-16
| | | | | | Problem: Test64 is old style. Solution: Convert to new style test. (Yegappan Lakshmanan, closes vim/vim#5363) https://github.com/vim/vim/commit/f9cb05c14753d984f002c0c090688f8510147e6b
* defaults: set nostartoflineMatthieu Coudron2019-12-03
| | | | | | | Having the cursor change column can be surprising. Force startofline in functional and old tests. Remove the functional breakindent test, as it's a subset of the oldtest one.
* tests: remove some redundant legacy tests #11028Daniel Hahler2019-10-26
| | | | These were turned into new-style Vim tests in cbecae46f.
* tests: fix non-controversial misuse of `pending` (#11247)Daniel Hahler2019-10-18
| | | Ref: https://github.com/neovim/neovim/pull/11184
* tests/ui: remove unnecessary screen:detach()Björn Linse2019-10-13
| | | | | | | | | | | | | It is perfectly fine and expected to detach from the screen just by the UI disconnecting from nvim or exiting nvim. Just keep detach() in screen_basic_spec, to get some coverage of the detach method itself. This avoids hang on failure in many situations (though one could argue that detach() should be "fast", or at least "as fast as resize", which works in press-return already). Never use detach() just to change the size of the screen, try_resize() method exists for that specifically.
* tests/ui: cleanup illegitimate usages of "attr_ignore"Björn Linse2019-10-13
| | | | | "attr_ignore" is an anti-pattern, with snapshot_util() just include all the highlights already.
* vim-patch:8.1.0460: assert_fails() message argument #11051Jan Edmund Lazo2019-09-21
| | | | | Problem: assert_fails() does not take a message argument Solution: Add the argument. https://github.com/vim/vim/commit/1307d1c003b01b4f67524c95feb07c3d91c7c428
* vim-patch:8.0.1770: assert functions don't return anythingJan Edmund Lazo2019-09-16
| | | | | | Problem: Assert functions don't return anything. Solution: Return non-zero when the assertion fails. https://github.com/vim/vim/commit/65a5464985f980d2bbbf4e14d39d416dce065ec7
* Merge #10869 'vim-patch:8.1.{0309,0362,0365,0515,1946}'Justin M. Keyes2019-09-05
|\
| * Change test because maparg was changed to also return lnumerw72019-09-04
| |
* | test: is_os() #10933Justin M. Keyes2019-09-04
|/ | | | | - Move os_name() up to "global helpers". - Rename it to is_os(). - Make it depend on uname() instead of a running Nvim instance.
* vim-patch:8.1.0888: the a: dict is not immutable as documented (#10819)Abdelhakeem Osama2019-08-21
| | | | | | Problem: The a: dict is not immutable as documented. Solution: Make the a:dict immutable, add a test. (Ozaki Kiichi, Yasuhiro Matsumoto, closes vim/vim#3929) https://github.com/vim/vim/commit/31b816042fca879b11965ddd75287732563ba698
* vim-patch:8.0.1738: ":args" output is hard to readDaniel Hahler2019-07-24
| | | | | | | | | | | | | | | Problem: ":args" output is hard to read. Solution: Make columns with the names if the output is more than one line. https://github.com/vim/vim/commit/5d69da462f584a3aefb3427b127334bf9af3a4b0 vim-patch:8.0.1740: warning for signed-unsigned incompatibility Problem: Warning for signed-unsigned incompatibility. Solution: Change type from "char *" to "char_u *". (John Marriott) https://github.com/vim/vim/commit/405dadb63ea2b7aa4c8c659807506a35a8a9504c Removes ported legacy test that was re-added later. Ref: https://github.com/neovim/neovim/pull/10147#issuecomment-512609513
* vim-patch:8.1.0211: expanding a file name "~" results in $HOMEJan Edmund Lazo2019-05-25
| | | | | | Problem: Expanding a file name "~" results in $HOME. (Aidan Shafran) Solution: Change "~" to "./~" before expanding. (closes vim/vim#3072) https://github.com/vim/vim/commit/00136dc321586800986e8f743c2f108f5eecbf92
* test: clear(): `args_rm` parameterJustin M. Keyes2019-04-27
|
* vim-patch:8.0.1510: cannot assert beep #9938Jan Edmund Lazo2019-04-25
| | | | | Problem: Cannot test if a command causes a beep. Solution: Add assert_beeps(). https://github.com/vim/vim/commit/b48e96f61c87a64e38e3ac50732c92a84a4833b8
* API: don't directly call update_screen() in API functionsBjörn Linse2019-01-08
| | | | | | | | | There is no need to call update_screen() directly in an API function, mode input processing invokes update_screen() as needed. And if the API call is done in a context where redraw is disabled, then redraw is disabled for a reason. A lot of API functions are of equal semantical strength (nvim_call_function and nvim_execute_lua can also do whatever, nvim_command is not special), this inconsistency has no purpose.
* vim-patch:8.1.0354: packadd test fails on MS-WindowsJames McCoy2018-12-29
| | | | | | Problem: Packadd test fails on MS-Windows. Solution: Ignore difference between forward and backward slashes. https://github.com/vim/vim/commit/53c8a478cc4265549597b00214e0da812154742e
* vim-patch:8.1.0353: an "after" directory of a package is appended to 'rtp'James McCoy2018-12-29
| | | | | | | | Problem: An "after" directory of a package is appended to 'rtp', which will be after the user's "after" directory. () Solution: Insert the package "after" directory before any other "after" directory in 'rtp'. (closes vim/vim#3409) https://github.com/vim/vim/commit/99396d4cbf78d313a454c7448acc07412d2e45b7
* vim-patch:8.0.1734: package directory not added to 'rtp' if prefix matchesJames McCoy2018-12-29
| | | | | | | Problem: Package directory not added to 'rtp' if prefix matches. Solution: Check the match is a full match. (Ozaki Kiichi, closes vim/vim#2817) Also handle different ways of spelling a path. https://github.com/vim/vim/commit/f98a39ca57d001ba3e24831bae1e375790fb41f0
* vim-patch:8.0.1469: when package path is a symlink 'runtimepath' is wrongJames McCoy2018-12-29
| | | | | | | | Problem: When package path is a symlink adding it to 'runtimepath' happens at the end. Solution: Do not resolve symlinks before locating the position in 'runtimepath'. (Ozaki Kiichi, closes vim/vim#2604) https://github.com/vim/vim/commit/2374faae111057ee28e8d487f9a52a95855e2206
* vim-patch:8.1.0550: expression evaluation may repeat an error messageJan Edmund Lazo2018-11-30
| | | | | | | | Problem: Expression evaluation may repeat an error message. (Jason Franklin) Solution: Increment did_emsg and check for the value when giving an error for the echo command. https://github.com/vim/vim/commit/76a6345433bc2a600689397fb28165a2e5793720
* functionaltest: enable FilterReadPre,FilterReadPost testJan Edmund Lazo2018-10-31
|
* functionaltests: win: enable gzip testJan Edmund Lazo2018-10-31
| | | | Close gzip file handles.
* test: Improve 008_autocommands_spec reliability (#9129)Justin M. Keyes2018-10-17
| | | | | | | | | | | | Sometimes 008_autocommands_spec fails like this: [ RUN ] autocommands that delete and unload buffers: BufUnload, VimLeave: -- Output to stderr: CMake Error at /home/travis/build/neovim/neovim/cmake/RunTests.cmake:53 (message): functional tests failed with error: 1 The final :quit + wait() is a race. Use command() instead, which is synchronous. Use command('silent! ...') everywhere else too, because it's clearer instead of feeding input and clearing the expected errors with CTRL-L.
* tests: improve robustness of immediate successes in screen testsBjörn Linse2018-10-15
|
* vim-patch:8.0.1291: C indent wrong when * immediately follows commentJan Edmund Lazo2018-08-20
| | | | | | Problem: C indent wrong when * immediately follows comment. (John Bowler) Solution: Do not see "/*" after "*" as a comment start. (closes vim/vim#2321) https://github.com/vim/vim/commit/f8c53d3d268fc67a29c8c1a4e76fae85762e11b5
* oldtests: finish port of 8.0.1224Jan Edmund Lazo2018-08-15
|
* vim-patch:8.0.1398: :packadd does not load packages from the "start" ↵Jan Edmund Lazo2018-07-23
| | | | | | | | | directory (#8762) Problem: :packadd does not load packages from the "start" directory. (Alejandro Hernandez) Solution: Make :packadd look in the "start" directory if those packages were not loaded on startup. https://github.com/vim/vim/commit/9e1d399e63903c6f84d7888ad8d84ebf4e29d8a1
generated by cgit (git 2.34.1) at 2025-07-06 02:00:30 +0000