aboutsummaryrefslogtreecommitdiff
path: root/test/functional/legacy/utf8_spec.lua
Commit message (Collapse)AuthorAge
* test: improve test conventionsdundargoc2024-04-23
| | | | | | | | | Specifically, functions that are run in the context of the test runner are put in module `test/testutil.lua` while the functions that are run in the context of the test session are put in `test/functional/testnvim.lua`. Closes https://github.com/neovim/neovim/issues/27004.
* refactor(test): inject after_each differentlyLewis Russell2024-04-10
|
* test: improve test conventionsdundargoc2024-04-08
| | | | Work on https://github.com/neovim/neovim/issues/27004.
* 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
* A Mudholland Dr. RecastBjörn Linse2020-10-19
| | | | | The commit summary maybe does not make sense, but calling a function that does not wait on anything `wait()` makes even less sense.
* test: lint whitespace in legacy/ (#7308)KillTheMule2017-09-24
|
* functests: Replace execute with either command or feed_commandZyX2017-04-09
| | | | | | | | | | Hope this will make people using feed_command less likely: this hides bugs. Already found at least two: 1. msgpackparse() will show internal error: hash_add() in case of duplicate keys, though it will still work correctly. Currently silenced. 2. ttimeoutlen was spelled incorrectly, resulting in option not being set when expected. Test was still functioning somehow though. Currently fixed.
* functests: Check logs in lua codeZyX2016-06-10
| | | | | | It is otherwise impossible to determine which test failed sanitizer/valgrind check. test/functional/helpers.lua module return was changed so that tests which do not provide after_each function to get new check will automatically fail.
* vim-patch:7.4.932watiko2016-02-16
| | | | | | | Problem: test_utf8 has confusing dummy command. Solution: Use a real command instead of a colon. https://github.com/vim/vim/commit/8f08dab18df6dbf6c4b4973fd2d480e4bffb82d8
* vim-patch:7.4.926watiko2016-02-16
| | | | | | | | | Problem: Completing the longest match doesn't work properly with multi-byte characters. Solution: When using multi-byte characters use another way to find the longest match. (Hirohito Higashi) https://github.com/vim/vim/commit/4f8fa1633cdfbd09a41160c8480fe67c198067e9
* vim-patch:7.4.755Jurica Bradaric2016-02-09
| | | | | | | | Problem: It is not easy to count the number of characters. Solution: Add the skipcc argument to strchars(). (Hirohito Higashi, Ken Takata) https://github.com/vim/vim/commit/641e48c2248ccb3c25a5cdaa3709f16152d8c77d
* encoding: Update handling of encoding in testsBjörn Linse2015-09-08
| | | | | | | Always run tests with encoding=utf-8, regardless of user locale Don't set &encoding after startup in tests Helped-By: Michael Reed <m.reed@mykolab.com>
* legacy tests: migrate test_utf8Rainer Borene2014-11-04