aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/testdir/test_utf8.vim
Commit message (Collapse)AuthorAge
* vim-patch:8.2.3545: setcellwidths() may make 'listchars' or 'fillchars' invalidzeertzjq2022-08-08
| | | | | | | | | Problem: setcellwidths() may make 'listchars' or 'fillchars' invalid. Solution: Check the value and give an error. (closes vim/vim#9024) https://github.com/vim/vim/commit/94358a1e6e640ca5ebeb295efdddd4e92b700673 Cherry-pick f_setcellwidths() change from patch 9.0.0036. Cherry-pick 'ambiwidth' docs update from runtime update 079ba76ae7a7.
* vim-patch:8.2.1537: memory acccess error when using setcellwidths()zeertzjq2022-08-08
| | | | | | Problem: Memory acccess error when using setcellwidths(). Solution: Use array and pointers correctly. https://github.com/vim/vim/commit/b06a6d59d12dbd67d55b3c46f6e5547e9103c931
* vim-patch:8.2.1535: it is not possible to specify cell widths of characterszeertzjq2022-08-08
| | | | | | | | Problem: It is not possible to specify cell widths of characters. Solution: Add setcellwidths(). https://github.com/vim/vim/commit/08aac3c6192f0103cb87e280270a32b50e653be1 Co-Authored-By: delphinus <me@delphinus.dev>
* vim-patch:8.2.4152: block insert with double wide character failsSean Dewar2022-02-14
| | | | | | Problem: Block insert with double wide character fails. Solution: Adjust the expected output. https://github.com/vim/vim/commit/fc6ccebea668c49e9e617e0657421b6a8ed9df1e
* vim-patch:8.2.4002: first char typed in Select mode can be wrongzeertzjq2022-01-24
| | | | | | | | | | | | Problem: First char typed in Select mode can be wrong. Solution: Escape special bytes in the input buffer. (closes vim/vim#9469) https://github.com/vim/vim/commit/6cac77016b1636e04073e8348b7cee02259ef928 The `buf` should already be large enough, but I'll change its size anyway in case future patches change the meaning of `MB_MAXBYTES` macro. `fix_input_buffer()` cannot be used here because of the `using_script()` check, and there is already equivalent code in its place.
* feat(eval/method): partially port v8.1.2004Sean Dewar2021-11-26
| | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make various functions usable as a method. https://github.com/vim/vim/commit/f6ed61e1489e40eada55a4f1782e1ed82bcad7d9 +sound is needed for sound_* functions. Make swapinfo and swapname take exactly one argument. Previously, they could erroneously take one or more.
* feat(eval/method): partially port v8.1.1993Sean Dewar2021-11-26
| | | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make various functions usable as a method. https://github.com/vim/vim/commit/196b4664432f932625cfb6371dc42c24efe6c203 server2client requires +clientserver, which hasn't been ported yet. The eval.txt docs and test_clientserver.vim tests for server2client already exist, so include those changes. test_bufline.vim: Test for setbufline requires v8.1.1189 (which was reverted in #10848).
* feat(eval/method): partially port v8.1.1954Sean Dewar2021-10-03
| | | | | | | | | | | Does not include listener_*() functions. js_*() functions are N/A. json_encode() and json_decode() didn't include tests; add some anyway (to json_functions_spec.lua). test_lua.vim isn't included yet, so add tests to luaeval_spec.lua.
* vim-patch:8.1.1079: no need for a separate ScreenLinesUtf8() test functionzeertzjq2021-09-19
| | | | | | Problem: No need for a separate ScreenLinesUtf8() test function. Solution: Get the composing characters with ScreenLines(). https://github.com/vim/vim/commit/48aed0824e47147faf19fc235ad4bcf851584c9c
* vim-patch:8.1.1071: cannot get composing characters from the screenzeertzjq2021-09-19
| | | | | | | Problem: Cannot get composing characters from the screen. Solution: Add screenchars() and screenstring(). (partly by Ozaki Kiichi, closes vim/vim#4059) https://github.com/vim/vim/commit/2912abb3a2fd72074e3901c8ae1d4a77ce764675
* vim-patch:8.2.1822: list test doesn't failJan Edmund Lazo2021-04-08
| | | | | | | | | | | Problem: List test doesn't fail. Solution: Adjust the test for NULL list handling. https://github.com/vim/vim/commit/f57497276bc616d3856eeff9824c080941faa51b Comment out test cases that modify null lists because Neovim throws error messages instead of silently failing. Null lists should be read-only and constant. https://github.com/neovim/neovim/issues/4615
* vim-patch:8.2.2078: illegal memory access when using :print on invalid textJan Edmund Lazo2020-12-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Illegal memory access when using :print on invalid text. (Dhiraj Mishra) Solution: Check for more composing characters than supported. (closes vim/vim#7399) https://github.com/vim/vim/commit/1cbfc9914db1cb06aaa092fa42eb7a2fc3dc7ad7 N/A patches for version.c: vim-patch:8.1.1013: MS-Windows: Scrolling fails when dividing the screen Problem: MS-Windows: Scrolling fails when dividing the screen. Solution: Position the cursor before calling ScrollConsoleScreenBuffer(). (Nobuhiro Takasaki, closes vim/vim#4115) https://github.com/vim/vim/commit/3b5fef6a995f25a8a8f746896de44df49b69dfdf vim-patch:8.1.1774: test is silently skipped Problem: Test is silently skipped. Solution: Throw "Skipped". https://github.com/vim/vim/commit/3c610c96389bbb5f0fc83f0a515fc8f1b7f515e4 vim-patch:8.2.1164: text cleared by checking terminal properties not redrawn Problem: Text cleared by checking terminal properties not redrawn. (Alexey Radkov) Solution: Mark the screen characters as invalid. (closes vim/vim#6422) https://github.com/vim/vim/commit/96916ac67ad9ed5d79ce87b099f9d01aa4c13745 vim-patch:8.2.2076: MS-Windows console: sometimes drops typed characters Problem: MS-Windows console: sometimes drops typed characters. Solution: Do not wait longer than 10 msec for input. (issue vim/vim#7164) https://github.com/vim/vim/commit/c478ee3d83fab0dba46740f2023c35f743f88316 vim-patch:8.2.2077: build failure with small features Problem: Build failure with small features. Solution: Add #ifdef. https://github.com/vim/vim/commit/a452b808b4da2d272ca4a50865eb8ca89a58f239 vim-patch:8.2.2086: libvterm tests are only run on Linux Problem: Libvterm tests are only run on Linux. Solution: Use static libraries. (Ozaki Kiichi, closes vim/vim#7419) https://github.com/vim/vim/commit/476268c387a05cfda9feaca8d1a5eeb535ed9f49
* test/old: partial port of patch 8.1.0711Jan Edmund Lazo2020-11-30
| | | | Patch 8.1.0711 is too difficult to merge in 1 commit.
* 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.0811: too many #ifdefsDaniel Hahler2019-08-22
| | | | | | Problem: Too many #ifdefs. Solution: Graduate FEAT_MBYTE, the final chapter. https://github.com/vim/vim/commit/30276f2beb248557c6b33cd5418bca8b7084b0a5
* vim-patch:8.0.0250James McCoy2017-03-24
Problem: When virtcol() gets a column that is not the first byte of a multi-byte character the result is unpredictable. (Christian Ludwig) Solution: Correct the column to the first byte of a multi-byte character. Change the utf-8 test to new style. https://github.com/vim/vim/commit/0c0590d9827cb07a33c1552cb3558b94bddcb4dc Closes #6269
generated by cgit (git 2.34.1) at 2026-10-20 13:12:22 +0000