aboutsummaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
* unittests: Use more adequate names for some functionsZyX2017-03-12
|
* tests: Allow lfs.attributes to be NULL when traversing FSZyX2017-03-12
|
* unittests: Fix linter errorsZyX2017-03-11
|
* unittests: Update test/unit/message_spec.luaZyX2017-03-11
|
* unittests: Do not use which, add data to paths.lua.in insteadZyX2017-03-11
|
* unittests: Always close all pipesZyX2017-03-11
|
* unittests: Do not import libnvim or headers in main processZyX2017-03-11
| | | Slows down unit tests much, but gets rid of as much preserved state as possible.
* unittests: Check core dumps in after_each, like in functestsZyX2017-03-11
|
* unittests: Run all unit tests in their own processesZyX2017-03-11
| | | | | | | | | | | | | | | Used sed -r -i -e '/ helpers =/ s/$/\nlocal itp = helpers.gen_itp(it)/; s/^(\s*)it\(/\1itp(/' test/unit/**/*_spec.lua to alter all tests. Locally they all run fine now. Reasoning: 1. General: state from one test should not affect other tests. 2. Local: travis build is failing with something which may be an output of garbage collector. This should prevent state of the garbage collector from interferring as well.
* unittests: Do not run failing test at allZyX2017-03-11
|
* unittests: Fix lint errorsZyX2017-03-11
|
* unittests: Allow failing test to failZyX2017-03-11
|
* unittests: Log syscalls if requestedZyX2017-03-11
|
* unittests: Use own bindings to libc syscall wrappersZyX2017-03-11
|
* unittests: Do not use syscall library: does not work well with cimportZyX2017-03-11
|
* unittests: Try using syscall library instead (ffi-based)ZyX2017-03-11
|
* unittests: Pause garbage collector while executing testsZyX2017-03-11
| | | Temporary (?) workaround for currently failing check_alloc_log tests.
* unittests: Run tests in a separate processZyX2017-03-11
|
* test/scrollback: wiggle-room (#6256)Justin M. Keyes2017-03-11
|
* rplugin: Call s:LoadRemotePlugins() on startup.Justin M. Keyes2017-03-11
| | | | | | | | | | Dispense with the FuncUndefined/CmdUndefined quasi-optimization. If there are no rplugins, plugin/rplugin.vim takes less than 1ms. Closes #5821 Closes #6250 Helped-by: Qiming zhao <chemzqm@gmail.com>
* test/let_spec: self-referencing List. (#6228)Justin M. Keyes2017-03-08
| | | Regression test coverage for #6070.
* Merge pull request #6225 from jamessan/vim-7.4.2051James McCoy2017-03-07
|\ | | | | vim-patch:7.4.2051,7.4.2068,7.4.2097
| * vim-patch:7.4.2068James McCoy2017-03-06
| | | | | | | | | | | | | | | | | | Problem: Not all arguments of trunc_string() are tested. Memory access error when running the message tests. Solution: Add another test case. (Yegappan Lakshmanan) Make it easy to run unittests with valgrind. Fix the access error. https://github.com/vim/vim/commit/b9644433d2728e99fab874e5e33147ad95d23a31
| * vim-patch:7.4.2051James McCoy2017-03-06
| | | | | | | | | | | | | | Problem: No proper testing of trunc_string(). Solution: Add a unittest for message.c. https://github.com/vim/vim/commit/502ae4ba63561c98ac69af26cd9883bfd18d225f
* | api: nvim_buf_set_lines(): Avoid invalid ml_get. #6019Matthew Malcomson2017-03-07
| | | | | | | | | | | | | | | | | | | | When the buffer that nvim_buf_set_lines() is changing is not in any vim window, fix_cursor() leads to calling ml_get_buf() with an invalid line number. The condition that fix_cursor() was called on was (buf == curbuf), but this is always true because of the call to switch_to_win_for_buf() earlier in the function. Instead this should be predicated on (save_curbuf.br_buf == NULL)
* | test: backtick expansion #6218Justin M. Keyes2017-03-06
|/
* terminal.c: Reset cursor postion when using termopen() (#6212)oni-link2017-03-04
| | | | | | | | | | After using 'termopen("echo") the current buffer content is changed, but the cursor position of the current window is not updated. Because of this, a call to 'mb_adjust_cursor()' can lead to a heap-buffer-overflow. Fix this by resetting the cursor for the current window. Fixes #3161
* vim-patch:8.0.0388Matthew Malcomson2017-03-02
| | | | | | | | | | | | | | | | Fix a problem when filtering manually folded lines When foldMarkAdjustRecurse() is called to adjust folds that start inside the range of lines that are being moved and end outside that range, it calculates `amount_after` for its recursive call incorrectly. The calculation assumes that folds inside the changed range are being deleted, but this is not always the case. This means nested folds that start after the changed range of lines are shifted an incorrect amount. We fix this by calculating the `amount_after` differently if the folds inside the changed range are not being deleted.
* test: luacheck updateJustin M. Keyes2017-03-01
| | | | | We pull luacheck HEAD, so this is a "catch up" commit to fix newly-discovered errors.
* terminal: Keep cursor position.Justin M. Keyes2017-03-01
| | | | | | Let the terminal dictate the normal-mode cursor position. This will be disorienting sometimes, but it is closer to what users expect vs always going to the last line.
* Merge #6191 from jamessan/vim-42ebd06Justin M. Keyes2017-02-28
|\ | | | | vim-patch:42ebd06,7.4.2098,6f1d9a0,7.4.2095
| * vim-patch:7.4.2095James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | Problem: Man test fails when run with the GUI. Solution: Adjust for different behavior of GUI. Add assert_inrange(). https://github.com/vim/vim/commit/61c04493b00f85d0b97436260a9ef9ab82143b78 Only changes related to assert_inrange() were included, since we have a distinct man plugin.
* | test: Refactor fold tests (#5993)Matthieu Coudron2017-02-28
|/
* edit.c: CTRL-SPC: Insert previously-inserted text. #6090Matthew Malcomson2017-02-28
| | | | | | | | | | | | | Default Vim behavior of i_CTRL-<Space> is to insert the last-inserted text and exit insert mode. :help i_CTRL-@ Before this commit that did not happen because insert_handle_key() checks for NUL instead of checking for ' ' with a CTRL `mod_mask`. I'm leaving the check for NUL despite the fact that at the moment that key is never seen when using the terminal UI (not for C-Space, nor C-@). This is because I assume it's still allowed for other front-ends to pass NUL, but at the moment the terminal UI isn't.
* vim-patch:7.4.2200James McCoy2017-02-27
| | | | | | | | Problem: Cannot get all information about a quickfix list. Solution: Add an optional argument to get/set loc/qf list(). (Yegappan Lakshmanan) https://github.com/vim/vim/commit/d823fa910cca43fec3c31c030ee908a14c272640
* Merge #6112 from ZyX-I/split-eval'/buf_get_changedtickJustin M. Keyes2017-02-27
|\ | | | | Better b:changedtick support
| * buffer: Hide one of the asserts from lua parserZyX2017-02-25
| |
| * *: Fix linter errorsZyX2017-02-23
| |
| * api: Make sure dict_set_var doesn’t edit read-only valuesZyX2017-02-23
| | | | | | Fixes #6147
| * functests: Destroy accidental folds in api/vim_specZyX2017-02-23
| |
| * eval: Forbid (un)locking b:changedtickZyX2017-02-23
| | | | | | Port of vim-patch:8.0.0343
| * eval: Make sure `islocked('b:.changedtick')` does not error outZyX2017-02-23
| | | | | | Port of vim-patch:8.0.0345
| * eval: Specify more precise len for var_check_ro in get_lvalZyX2017-02-23
| |
| * functests: Add some more testsZyX2017-02-23
| |
| * buffer: Forbid unletting b:changedtickZyX2017-02-23
| |
| * eval: Refactor item_lockZyX2017-02-23
| | | | | | If I am not mistaking, this commit should not change any functionality.
| * eval: Make sure that b:changedtick may not be unlocked via :unlo b:varZyX2017-02-23
| | | | | | It still may be unlocked by `:unlock b:.var`.
| * functests: Add testsZyX2017-02-23
| | | | | | Contains a number of FIXMEs.
| * buffer: Bind b:changedtick to b:['changedtick'], remove special casesZyX2017-02-23
| |
| * api/buffer: Add nvim_buf_get_changedtick methodZyX2017-02-23
| |
generated by cgit (git 2.34.1) at 2025-06-02 19:43:46 +0000