aboutsummaryrefslogtreecommitdiff
path: root/test/functional
Commit message (Collapse)AuthorAge
...
* | | | Tests: add errorlist_spec.luaMarco Hinz2016-02-25
| |_|/ |/| |
* | | Tests: fix according to lualintMarco Hinz2016-02-24
| | |
* | | bufhl: add tests for adding and clearing highlightsBjörn Linse2016-02-23
| |/ |/|
* | keymap: Support <D-...> (super/command key).Justin M. Keyes2016-02-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds support for: - api:vim_input("<D-a>") - ":nnoremap <C-D-S-...>" and permutations thereof UIs must capture the modifier and send it as "<D-...>" to vim_input(). Note: Before this commit, any arbitrary ":nnoremap <{foo}-{bar}>" mapping could already be invoked with feedkeys("\<{foo}-{bar}>"). This commit supports "D-" as a modifier that can be combined with "C-", "A-", "S-" in any order. For non-GUI (terminal) support, user must: :set <D-a>={CSI sequence} then send the {CSI sequence} from their terminal. But this does not work yet (regression #2204). Closes #2190
* | Merge pull request #4267 from watiko/vim-7.4.932Justin M. Keyes2016-02-22
|\ \ | | | | | | vim-patch:7.4.{926,932,933}
| * | 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
* | | Merge pull request #4262 from watiko/vim-7.4.893Justin M. Keyes2016-02-22
|\ \ \ | | | | | | | | vim-patch:7.4.{891,893,912}
| * | | vim-patch:7.4.912watiko2016-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Wrong indenting for C++ constructor. Solution: Recognize ::. (Anhong) https://github.com/vim/vim/commit/e01f4f86cef7bed3cb99b26f9f57d86f6eb5fe1a
| * | | vim-patch:7.4.893watiko2016-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: C indenting is wrong below a "case (foo):" because it is recognized as a C++ base class construct. Issue #38. Solution: Check for the case keyword. https://github.com/vim/vim/commit/d1b15dec4d00d7ed5e92ff4e0fb7fc2e0818e479
| * | | vim-patch:7.4.891watiko2016-02-15
| |/ / | | | | | | | | | | | | | | | | | | | | | Problem: Indentation of array initializer is wrong. Solution: Avoid that calling find_start_rawstring() changes the position returned by find_start_comment(), add a test. (Hirohito Higashi) https://github.com/vim/vim/commit/089af18d1fd0961ff504ee72db0156bbfe509cdf
* | | Merge pull request #4167 from lucc/test11Justin M. Keyes2016-02-21
|\ \ \ | | | | | | | | tests: migrate legacy test 11
| * | | test: Migrate legacy test 11.Lucas Hoffmann2016-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some parts of the test depend on gzip(1). They are skipped if gzip is not available. Some `:write` and `:edit` commands produce messages and "hit enter" prompts that had to be treated with an extra `feed('<C-L>')`. In the original test file this was not neccessary because it was `:source!`ed.
* | | | Merge pull request #4243 from lucc/test36Justin M. Keyes2016-02-21
|\ \ \ \ | | | | | | | | | | tests: Migrate legacy test 36.
| * | | | test: Migrate legacy test 36.Lucas Hoffmann2016-02-15
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | The test was split into several blocks reusing the same input file. As it is complicated to send text in different encodings and with control characters from the test suite to nvim and back the results are written to a temp file and loaded into the test from there.
* | | | Tests: check <abuf> from TermCloseMarco Hinz2016-02-21
| | | |
* | | | test: charsearch: Fix error/typo in legacy test.Lucas Hoffmann2016-02-20
| | | | | | | | | | | | | | | | | | | | Error was reported upstream in vim/vim#650, fixed in 7.4.1366. Typo was fixed upstream in 7.4.1041.
* | | | tests: Migrate legacy charsearch test.Lucas Hoffmann2016-02-20
| | | |
* | | | Merge pull request #4240 from jbradaric/vim-7.4.888Justin M. Keyes2016-02-19
|\ \ \ \ | | | | | | | | | | vim-patch:7.4.888
| * | | | test: Fix lint errorwatiko2016-02-15
| | | | |
| * | | | test: Add test cases to legacy test autocmd_optionwatiko2016-02-15
| | |/ / | |/| |
* / | | vim-patch:7.4.844 #4228Jurica Bradaric2016-02-17
|/ / / | | | | | | | | | | | | | | | | | | Problem: When '#' is in 'isident' the is# comparator doesn't work. Solution: Don't use vim_isIDc(). (Yasuhiro Matsumoto) https://github.com/vim/vim/commit/37a8de17d4dfd3d463960c38a204ce399c8e19d4
* | | Merge pull request #4220 from watiko/vim-7.4.792Justin M. Keyes2016-02-15
|\ \ \ | |/ / |/| | vim-patch:7.4.792
| * | tests: Migrate legacy test match_concealwatiko2016-02-11
| | |
* | | Merge #4140 'vim-patch:7.4.771'.Justin M. Keyes2016-02-15
|\ \ \
| * | | test: search_mbyte_spec: minor cleanupJustin M. Keyes2016-02-15
| | | | | | | | | | | | | | | | mbyte.vim, small.vim are not relevant to migrated legacy tests.
| * | | Remove unused variables from the test.Jurica Bradaric2016-02-01
| | | |
| * | | Use before_each instead of setup in the test.Jurica Bradaric2016-02-01
| | | |
| * | | Add test files for patch 7.4.771.Jurica Bradaric2016-02-01
| | | | | | | | | | | | | | | | vim-patch:efcabd6892ad89a4585fb77aa94c3b1802b784ab
* | | | Merge pull request #4166 from lucc/legacy/command_countJustin M. Keyes2016-02-15
|\ \ \ \ | | | | | | | | | | tests: Migrate legacy test command_count.
| * | | | tests: Simplify migrated legacy test.Lucas Hoffmann2016-02-04
| | | | |
| * | | | tests: Fix migrated legacy test.Lucas Hoffmann2016-02-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test involves argument and buffer numbers. Therefore it was necessary to use a custom testing session to ensure that the initial buffer corresponds to an argument.
| * | | | tests: Migrate legacy test command_count.Lucas Hoffmann2016-02-04
| | | | |
* | | | | Merge #2674Justin M. Keyes2016-02-13
|\ \ \ \ \
| * | | | | test: completion_spec: minor editsJustin M. Keyes2016-02-13
| | | | | |
| * | | | | tests: add always complete testsolawing2016-01-29
| | | | | |
* | | | | | test: shada_spec: resolve symlinkJun T2016-02-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the build directory path has symlinks in it, 'make functionaltest' fails at shada_spec.lua:177 because readme_fname has symlink but nvim resolves the symlink when writing it into the shada file.
* | | | | | Merge pull request #4204 from watiko/vim-7.4.915Justin M. Keyes2016-02-11
|\ \ \ \ \ \ | | | | | | | | | | | | | | vim-patch:7.4.{749,915}
| * | | | | | vim-patch:7.4.915watiko2016-02-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: When removing from 'path' and then adding, a comma may go missing. (Malcolm Rowe) Solution: Fix the check for P_ONECOMMA. (closes #471) https://github.com/vim/vim/commit/174674743d9a2d7361c9cd89836f8dd8651edeeb
* | | | | | | vim-patch:7.4.929watiko2016-02-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: "gv" after paste selects one character less if 'selection' is "exclusive". Solution: Increment the end position. (Christian Brabandt) https://github.com/vim/vim/commit/d29c6fea94947b3f4b54fbd5a6f832a7d744bf27
* | | | | | | vim-patch:7.4.743watiko2016-02-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: "p" in Visual mode causes an unexpected line split. Solution: Advance the cursor first. (Yukihiro Nakadaira) https://github.com/vim/vim/commit/c004bc2726eafc7a56d1d9f8398a65a0a7dc8d6c
* | | | | | | vim-patch:7.4.734watiko2016-02-11
| |_|_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: ml_get error when using "p" in a Visual selection in the last line. Solution: Change the behavior at the last line. (Yukihiro Nakadaira) https://github.com/vim/vim/commit/d009e8682686a56f7565e6e093a42cd0596e121f
* | | | | | vim-patch:7.4.834Jurica Bradaric2016-02-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: gettabvar() doesn't work after Vim start. (Szymon Wrozynski) Solution: Handle first window in tab still being NULL. (Christian Brabandt) https://github.com/vim/vim/commit/7e47d1ac6a9ae0e5a7167aa34ff651a9c39c1641
* | | | | | 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
* | | | | Merge pull request #4175 from watiko/vim-7.4.700Justin M. Keyes2016-02-07
|\ \ \ \ \ | | | | | | | | | | | | vim-patch:7.4.700
| * | | | | tests: Add test case for legacy test 45watiko2016-02-05
| | | | | |
| * | | | | tests: Migrate legacy test 45.Lucas Hoffmann2016-02-05
| | | | | |
* | | | | | Merge pull request #4157 from watiko/vim-7.4.694Justin M. Keyes2016-02-05
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | vim-patch:7.4.{662,694}
| * | | | | tests: Migrate legacy test textobjectswatiko2016-02-03
| |/ / / /
* / / / / ui: revert "gui_running" hackJustin M. Keyes2016-02-03
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Plugins (YCM, dispatch.vim) use gui_running to decide behavior; so do some colorschemes. Up to now, nvim lied about gui_running for the benefit of colorschemes and the detriment of all _other_ plugins that check this condition. That's counterproductive: a user employs at most _one_ colorscheme but may use many other plugins which expect the Vim legacy semantics of gui_running. Moreover, colorschemes usually don't _need_ to check gui_running: they can instead set cterm{fg,bg} and gui{fg,bg} in the same :highlight call. It is reasonable for users who want "true color" to modify their colorscheme once (or request upstream to do so) in order to avoid running into quirks in any other plugins. Closes #2782
generated by cgit (git 2.34.1) at 2025-07-12 05:19:40 +0000