aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/testdir
Commit message (Collapse)AuthorAge
...
* vim-patch:8.1.1122: char2nr() does not handle composing charactersJan Edmund Lazo2020-02-20
| | | | | | | | Problem: char2nr() does not handle composing characters. Solution: Add str2list() and list2str(). (Ozaki Kiichi, closes vim/vim#4190) https://github.com/vim/vim/commit/9d40128afd7fcd038ff6532722b55b1a8c189ce8 'utf8' optional param is noop unlike Vim.
* vim-patch:8.1.1868: multi-byte chars in 'listchars' fail with 'linebreak' setJan Edmund Lazo2020-02-20
| | | | | | | | Problem: Multibyte characters in 'listchars' don't work correctly if 'linebreak' is also enabled. (Martin Tournoij) Solution: Make it work correctly. (Christian Brabandt, closes vim/vim#4822, closes vim/vim#4812) https://github.com/vim/vim/commit/69cbbecf548f390197259ca30cfe147c3e59ce5a
* vim-patch:8.2.0267: no check for a following cmd when calling a function failsJan Edmund Lazo2020-02-16
| | | | | | | Problem: No check for a following command when calling a function fails. Solution: Also check for a following command when inside a try block. (closes vim/vim#5642) https://github.com/vim/vim/commit/e51bb17dd0d51384375830ee2a1df30c08121443
* vim-patch:8.1.0043: ++bad argument of :edit does not work properlyJan Edmund Lazo2020-02-16
| | | | | | | | Problem: ++bad argument of :edit does not work properly. Solution: Return FAIL from get_bad_opt() only when there is no valid argument. (Dominique Pelle, Christian Brabandt, closes vim/vim#2966, closes vim/vim#2947) https://github.com/vim/vim/commit/7580849df9d6c7c515f5ed784019336d8a8ec0f0
* vim-patch:8.1.2187: error for bad regexp even though regexp is not usedJan Edmund Lazo2020-02-16
| | | | | | | Problem: Error for bad regexp even though regexp is not used when writing a file. (Arseny Nasokin) Solution: Ignore regexp errors. (closes vim/vim#5059) https://github.com/vim/vim/commit/b40c2576d4e0e2dd2c580414c45947d88556d76d
* vim-patch:8.2.0241: crash when setting 'buftype' to "quickfix"Jan Edmund Lazo2020-02-16
| | | | | | Problem: Crash when setting 'buftype' to "quickfix". Solution: Check that error list is not NULL. (closes vim/vim#5613) https://github.com/vim/vim/commit/99234f29aa8767f2e71bb1f5db6ee0131bc8e64e
* vim-patch:8.1.2259: running tests may leave XfakeHOME behindJan Edmund Lazo2020-02-16
| | | | | | | Problem: Running tests may leave XfakeHOME behind. Solution: Source summarize.vim without using setup.vim. (closes vim/vim#5177) Also fix that on MS-Windows the test log isn't echoed. https://github.com/vim/vim/commit/7d2320414ffdd698c9a17d775f71e2c455c21624
* vim-patch:8.1.2131: MSVC tests failJan Edmund Lazo2020-02-16
| | | | | | Problem: MSVC tests fail. Solution: Replace backslashes with slashes. https://github.com/vim/vim/commit/c25e702deec74771e49f6c2df4cda7a1f97d0c1e
* vim-patch:8.1.2129: using hard coded executable path in testJan Edmund Lazo2020-02-16
| | | | | | | Problem: Using hard coded executable path in test. Solution: Use v:progpath. Use $VIMRUNTIME instead of "runtime". (James McCoy, closes vim/vim#5025) https://github.com/vim/vim/commit/1ac41a5c1352306942344777d2ba86dccd84ffad
* vim-patch:8.2.0235: draw error when an empty group is removed from 'statusline'Björn Linse2020-02-09
| | | | | | Problem: Draw error when an empty group is removed from 'statusline'. Solution: Do not use highlighting from a removed group. https://github.com/vim/vim/commit/dbe5d361feb65137099644329cf0ecfd4a945a14
* vim-patch:8.2.0161: not recognizing .gv file as dot filetypeJan Edmund Lazo2020-02-01
| | | | | | Problem: Not recognizing .gv file as dot filetype. Solution: Add *.gv to dot pattern. (closes vim/vim#5544) https://github.com/vim/vim/commit/f8ddb25789a6af530e69f499907979dfbff1c1ea
* vim-patch:8.2.0190: detect Kotlin files [ci skip] #11796Alkeryn2020-02-01
| | | | | Problem: Kotlin files are not recognized. Solution: Detect Kotlin files. (Alkeryn, closes vim/vim#5560) https://github.com/vim/vim/commit/ab067a21b9622513ed75f4801b001606eeaf2474
* vim-patch:8.2.0016: test name used twice, option not restored properlyJan Edmund Lazo2020-01-30
| | | | | | Problem: Test name used twice, option not restored properly. Solution: Rename function, restore option with "&". https://github.com/vim/vim/commit/a48e78e11f2b647183fd12f569020756b17d7683
* vim-patch:8.2.0014: test69 and test95 are old styleJan Edmund Lazo2020-01-30
| | | | | | Problem: Test69 and test95 are old style. Solution: Convert to new style tests. (Yegappan Lakshmanan, closes vim/vim#5365) https://github.com/vim/vim/commit/afc13bd8271819c7871ff2ae2cfebb22190a0d39
* vim-patch:8.2.0077: settagstack() cannot truncate at current indexJan Edmund Lazo2020-01-29
| | | | | | Problem: settagstack() cannot truncate at current index. Solution: Add the "t" action. (Yegappan Lakshmanan, closes vim/vim#5417) https://github.com/vim/vim/commit/271fa08a35b8d320d3a40db4ddae83b698fdd4fb
* vim-patch:8.1.0446: options test fails in the GUIJan Edmund Lazo2020-01-29
| | | | | | Problem: Options test fails in the GUI. Solution: Don't try changing 'term' in the GUI. https://github.com/vim/vim/commit/4f888757257795969f2ab2e6fc3544a5bef3cdea
* vim-patch:8.1.0445: setting 'term' does not store location for termcap optionsJan Edmund Lazo2020-01-29
| | | | | | | Problem: Setting 'term' does not store location for termcap options. Solution: Set the script context for termcap options that are changed when 'term' is set. https://github.com/vim/vim/commit/35bc7d6c52f516b60d683bf9f0f57266d86e25b9
* vim-patch:8.2.0158: triggering CompleteDone earlier is not backwards compatibleJan Edmund Lazo2020-01-26
| | | | | | | Problem: Triggering CompleteDone earlier is not backwards compatible. (Daniel Hahler) Solution: Add CompleteDonePre instead. https://github.com/vim/vim/commit/3f169ce17e8b779d105c96138a8b4246f2d270b9
* vim-patch:8.1.1144: too strict checking of the 'spellfile' optionJan Edmund Lazo2020-01-26
| | | | | | Problem: Too strict checking of the 'spellfile' option. Solution: Allow for a path. https://github.com/vim/vim/commit/862f1e17eaf2b9c6617dfba31d8487cde462658d
* 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.1.2245: third character of 'listchars' tab shows in wrong placeJan Edmund Lazo2020-01-24
| | | | | | | Problem: Third character of 'listchars' tab shows in wrong place when 'breakindent' is set. Solution: Set c_final to NUL. (Naruhiko Nishino, closes vim/vim#5165) https://github.com/vim/vim/commit/2f7b7b1e123d505637d21e0df28eb9e92667479c
* vim-patch:8.2.0147: block Visual mode operators not correct when 'linebreak' setJan Edmund Lazo2020-01-24
| | | | | | Problem: Block Visual mode operators not correct when 'linebreak' set. Solution: Set w_p_lbr to lbr_saved more often. (Ken Takata, closes vim/vim#5524) https://github.com/vim/vim/commit/03c3bd9fd094c1aede2e8fe3ad8fd25b9f033053
* vim-patch:8.2.0146: wrong indent when 'showbreak' and 'breakindent' are setJan Edmund Lazo2020-01-23
| | | | | | | Problem: Wrong indent when 'showbreak' and 'breakindent' are set and 'briopt' includes "sbr". Solution: Reset "need_showbreak" where needed. (Ken Takata, closes vim/vim#5523) https://github.com/vim/vim/commit/dfede9a70b3136988a8f262742101ad5cb98f46d
* vim-patch:8.2.0141: no swift filetype detection (#11747)Jan Edmund Lazo2020-01-23
| | | | | Problem: No swift filetype detection. Solution: Add swift, swiftgyb and sil. (Emir Sarı, closes vim/vim#5517) https://github.com/vim/vim/commit/0d76683e094c6cac2e879601aff3acf1163cbe0b
* Merge #11735 ':tabs : show # for previous tabpage'Justin M. Keyes2020-01-19
|\
| * tabpage: :tabs indicates previous tabpage's curwinWe're Yet2020-01-19
| |
* | Merge #11737 from janlazo/vim-8.1.2421Justin M. Keyes2020-01-19
|\ \ | | | | | | vim-patch:8.1.{2031,2421}
| * | vim-patch:8.1.2421: test88 is old styleJan Edmund Lazo2020-01-19
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Test88 is old style. Solution: Turn into a new style test. (Yegappan Lakshmanan, closes vim/vim#5347) https://github.com/vim/vim/commit/213ed008bbcd9fe0d3329b17f5f4af0169e448ff 'test_conceal.vim' requires +conceal and +terminal so it is N/A.
* | | Merge pull request #11736 from bfredl/tencBjörn Linse2020-01-19
|\ \ \ | |/ / |/| | restore old 'termencoding' behavior
| * | restore old 'termencoding' behaviorBjörn Linse2020-01-19
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Partially reverts #11647. Replaces #11662 The old implementation was removed without clear motivation. The "term option" hackaround added in its place is neither shorter nor simpler. The new behavior breaks even init.vim that expliticly check against it: if exists('&termencoding') set termencoding=utf-8 endif There was nothing wrong with the 0.4.x behavior. Empty &tenc has indicated that the &enc value should be used for all the history of Nvim. Ignoring setting the option is the expected behavior for Vim versions that does not support the option (and Nvim is such a version) 'tenc' was also irrelevant to the Test_unicode python3 test. The reason this has to be disabled is that neovim can't change internal 'encoding'
* | vim-patch:8.2.0123: complete_info() does not work when CompleteDone is triggeredJan Edmund Lazo2020-01-17
| | | | | | | | | | | | Problem: complete_info() does not work when CompleteDone is triggered. Solution: Trigger CompleteDone before clearing the info. https://github.com/vim/vim/commit/17e04781f26c24769e202351c194ee252927eee1
* | vim-patch:8.1.1139: no test for what is fixed in patch 8.1.0716Jan Edmund Lazo2020-01-17
| | | | | | | | | | | | Problem: No test for what is fixed in patch 8.1.0716. Solution: Add a test. (Yasuhiro Matsumoto, closes vim/vim#3797) https://github.com/vim/vim/commit/9845f36aa6ba28e0aa388bb635d4bb8ab56f1a47
* | vim-patch:8.1.0716: get warning message when 'completefunc' returns nothingJan Edmund Lazo2020-01-17
| | | | | | | | | | | | | | Problem: Get warning message when 'completefunc' returns nothing. Solution: Allow for returning v:none to suppress the warning message. (Yasuhiro Matsumoto, closes vim/vim#3789) https://github.com/vim/vim/commit/cee9bc2e3dc5c16a9d2a8d0e23aa0d5fdefa3a4a
* | vim-patch:8.2.0120: virtcol() does not check arguments to be validJan Edmund Lazo2020-01-17
| | | | | | | | | | | | | | | | Problem: virtcol() does not check arguments to be valid, which may lead to a crash. Solution: Check the column to be valid. Do not decrement MAXCOL. (closes vim/vim#5480) https://github.com/vim/vim/commit/b3d33d8570bc49a7f90990572d7f9630a1bfae02
* | vim-patch:8.2.0112: illegal memory access when using 'cindent'Jan Edmund Lazo2020-01-17
|/ | | | | | Problem: Illegal memory access when using 'cindent'. Solution: Check for NUL byte. (Dominique Pelle, closes vim/vim#5470) https://github.com/vim/vim/commit/02ad46394e8f887b60fda994f8a5da2ac1937b23
* vim-patch:8.1.1309: test for Normal highlight fails on MS-Windows GUIJan Edmund Lazo2020-01-06
| | | | | | Problem: Test for Normal highlight fails on MS-Windows GUI. Solution: Skip the test for MS-Windows GUI. https://github.com/vim/vim/commit/6b528fa062a5ac6bb5d8bd3abc26f32c65691d00
* vim-patch:8.1.1308: the Normal highlight is not defined when compiled with GUIJan Edmund Lazo2020-01-06
| | | | | | Problem: The Normal highlight is not defined when compiled with GUI. Solution: Always define Normal. (Christian Brabandt, closes vim/vim#4072) https://github.com/vim/vim/commit/f90b6e03a983b62b66564fc449e32724d6456769
* vim-patch:8.1.1579: dict and list could be GC'ed while displaying errorJan Edmund Lazo2020-01-05
| | | | | | | | | Problem: Dict and list could be GC'ed while displaying error in a timer. (Yasuhiro Matsumoto) Solution: Block garbage collection when executing a timer. Add test_garbagecollect_soon(). Add "no_wait_return" to test_override(). (closes vim/vim#4571) https://github.com/vim/vim/commit/adc6714aac20f5462a0ecec50ab4806b2f3ab0db
* vim-patch:8.1.0851: feedkeys() with "L" does not work properlyJan Edmund Lazo2020-01-05
| | | | | | | Problem: feedkeys() with "L" does not work properly. Solution: Do not set typebuf_was_filled when using "L". (Ozaki Kiichi, closes vim/vim#3885) https://github.com/vim/vim/commit/8d4ce56a19ed14d13332f94ad592fff2d9a715d5
* vim-patch:8.1.0844: when timer fails test will hang foreverJan Edmund Lazo2020-01-03
| | | | | | Problem: When timer fails test will hang forever. Solution: Use reltime() to limit waiting time. (Ozaki Kiichi, closes vim/vim#3878) https://github.com/vim/vim/commit/50948e4ac24314d5a70404bbc592ffc28755ad9f
* vim-patch:8.1.0842: getchar_zero test fails on MS-WindowsJan Edmund Lazo2020-01-03
| | | | | | Problem: getchar_zero test fails on MS-Windows. Solution: Disable the test for now. https://github.com/vim/vim/commit/cb908a813cebf7fb4608ff43fc3d258cf2768809
* vim-patch:8.1.0840: getchar(0) never returns a character in the terminalJan Edmund Lazo2020-01-03
| | | | | | Problem: getchar(0) never returns a character in the terminal. Solution: Call wait_func() at least once. https://github.com/vim/vim/commit/12dfc9eef14fe74c46145aa9e6cba9666f1bcd40
* vim-patch:8.0.1817: a timer may change v:count unexpectedlyJan Edmund Lazo2020-01-03
| | | | | | | Problem: A timer may change v:count unexpectedly. Solution: Save and restore v:count and similar variables when a timer callback is invoked. (closes vim/vim#2897) https://github.com/vim/vim/commit/b0f42ba60d9e6d101d103421ba0c351811615c15
* vim-patch:8.2.0079: test still fails on MS-Windows #11663Jan Edmund Lazo2020-01-03
| | | | | Problem: Python 3 unicode test still fails on MS-Windows. Solution: Do not set 'encoding' to "euc-tw" on MS-Windows. https://github.com/vim/vim/commit/7fc4785ea19306b7e94beb61f226cf40c32b1aba
* option: restore termencoding (readonly) #11662Jan Edmund Lazo2020-01-02
| | | | 'termencoding' option was removed in abaabd1d03fd723630f6addeadee9928faa4cdde but some plugins check its value.
* vim-patch:8.2.0076: Python 3 unicode test fails on MS-WindowsJan Edmund Lazo2020-01-01
| | | | | | Problem: Python 3 unicode test fails on MS-Windows. Solution: Do not set 'encoding' to "debug" on MS-Windows. https://github.com/vim/vim/commit/955f4e6f36ea009b90803d12a62108c94f446778
* vim-patch:8.2.0075: Python 3 unicode test still sometimes failsJan Edmund Lazo2020-01-01
| | | | | | Problem: Python 3 unicode test still sometimes fails. Solution: Skip the test when 'termencoding' is not empty. https://github.com/vim/vim/commit/2466aea508f22d44099d54ed6d15c0a1d90f8d6e
* vim-patch:8.2.0074: Python 3 unicode test someitmes failsJan Edmund Lazo2020-01-01
| | | | | | Problem: Python 3 unicode test someitmes fails. Solution: Make 'termencoding' empty. Correct number of error message. https://github.com/vim/vim/commit/4b7cdca23035eacf6cd0e30b90546cf32f7efe9e
* vim-patch:8.2.0070: crash when using Python 3 with "debug" encodingJan Edmund Lazo2020-01-01
| | | | | | Problem: Crash when using Python 3 with "debug" encoding. (Dominique Pelle) Solution: Use "euc-jp" whenever enc_dbcs is set. https://github.com/vim/vim/commit/d518f952f0812778758b25139308bcf45df6988c
* vim-patch:8.2.0068: crash when using Python 3 with "utf32" encodingJan Edmund Lazo2019-12-31
| | | | | | Problem: Crash when using Python 3 with "utf32" encoding. (Dominique Pelle) Solution: Use "utf-8" whenever enc_utf8 is set. (closes vim/vim#5423) https://github.com/vim/vim/commit/556684ff71e044a642879d759373a7ebc5047fad
generated by cgit (git 2.34.1) at 2026-01-02 19:33:01 +0000