| Commit message (Collapse) | Author | Age |
... | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because the old name did not indicate that the function
would return true on directories as well.
|
| | | | | |
|
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: test_expand leaves files behind.
Solution: Edit another file before deleting, otherwise the swap file
remains.
https://github.com/vim/vim/commit/08b270a8a4544be9a7fecce311834fde2b457634
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
make timers work correctly when timeout or repeat is zero
|
| | | | | |
|
| | | | | |
|
| |/ / /
|/| | |
| | | |
| | | | |
Cf. https://github.com/neovim/neovim/pull/4995
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Wrong argument to assert_exception() causes a crash. (reported by
Coverity)
Solution: Check for NULL pointer. Add a test.
https://github.com/vim/vim/commit/da5dcd936656f524dd0ae7cb2685245f07f5720f
|
|\ \ \
| |/ /
|/| |
| | | |
Closes #4979
|
|/ /
| |
| |
| | |
Original patch by @fmoralesc
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It appears that used msgpack library is not able to parse back message created
by msgpack_rpc_from_object() if nesting level is too high, so log_server_msg now
cares about msgpack_unpack_next() return value. Also error message from
server_notifications_spec.lua is not readable if something is wrong (though at
least now it does not crash when parsing deeply nested structures).
log_server_msg() in the test reports
[msgpack-rpc] nvim -> client(1) [error] "parse error"
|
| | |
|
| |
| |
| |
| |
| |
| | |
This removes some stack overflows in new test regarding deeply nested variables.
Now in place of crashing vim_to_object/msgpack_rpc_from_object/etc it crashes
clear_tv with stack overflow.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This ought to prevent stack overflow, but I do not see this actually working:
*lua* code crashes with stack overflow when trying to deserialize msgpack from
Neovim, Neovim is fine even if nesting level is increased 100x (though test
becomes very slow); not sure how recursive function may survive this. So it
looks like there are currently only two positive effects:
1. NULL lists are returned as empty (#4596).
2. Functional tests are slightly more fast. Very slightly. Checked for Release
build for test/functional/eval tests because benchmarking of debug mode is
not very useful.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Actual value on FreeBSD is -31, UV_EMLINK was obtained from
/usr/include/asm-generic/errno-base.h (there EMLINK is defined as 31 there).
This may actually be something else, but I do not think so as “Too many links”
description also fits in. [Man page][1] agrees with me, search for `[EMLINK]`
([linux man page][2] also specifies ELOOP explicitly in a similar section).
[1]: https://www.freebsd.org/cgi/man.cgi?query=open&sektion=2
[2]: http://man7.org/linux/man-pages/man3/open.3p.html
|
| | |
|
| | |
|
| |
| |
| |
| | |
Also fixes some errors found.
|
| |
| |
| | |
New os/fs.c functions are now all tested.
|
| | |
|
| |
| |
| |
| | |
The test hit wait_return if x or .x.swp exists in the project root directory.
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Quickfix code using memory after being freed. (Dominique Pelle)
Solution: Detect that the window was closed. (Hirohito Higashi)
https://github.com/vim/vim/commit/0899d698030ec076eb26352cda1ea334ab0819d9
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Make matchparen_spec.lua fail if matchparen is not available
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
https://groups.google.com/forum/#!msg/vim_dev/H3Z3ChSUh_4/beZs6KzYdBsJ
|
| | | |
| | | |
| | | |
| | | | |
Also use less "regular" values for cterm colors.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
add tests for synIDattr() with [fg|bg|sp]#
add tests for synIDattr and various #RGB colors
synIDattr: test for ui_rgb_attached()
test: fix tests for synIDattr fg/bg/sp
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, the api metadata was only accessible frow within nvim as
msgpackparse(systemlist('nvim --api-info'))[0]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Can only get the directory of the current window.
Solution: Add window and tab arguments to getcwd() and haslocaldir().
(Thinca, Hirohito Higashi)
https://github.com/vim/vim/commit/c970330676eaae7ba7cd05cfa46df5a413853ef9
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
menu_spec.lua yanks to the clipboard, but never pastes from it. This
can leave a child xsel process waiting around for something to paste the
content, causing the test process to hang.
Since the test isn't explicitly trying to exercise the clipboard, simply
use the default register.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This new functionality is explained in the documentation.
Also, many tests have been added to the buffer_spec.lua file
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When skipping these test blocks they may error out:
Error → test/functional/shell/viml_system_spec.lua @ 154
system() with output containing NULs setup
./test/functional/helpers.lua:75: attempt to index upvalue 'session' (a nil value)
stack traceback:
./test/functional/helpers.lua:75: in function 'request'
./test/functional/helpers.lua:166: in function 'nvim_feed'
./test/functional/helpers.lua:195: in function 'feed'
test/functional/shell/viml_system_spec.lua:14: in function <test/functional/shell/viml_system_spec.lua:13>
Error → test/functional/shell/viml_system_spec.lua @ 155
system() with output containing NULs teardown
./test/functional/helpers.lua:75: attempt to index upvalue 'session' (a nil value)
stack traceback:
./test/functional/helpers.lua:75: in function 'eval'
test/functional/shell/viml_system_spec.lua:21: in function <test/functional/shell/viml_system_spec.lua:20>
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add both a test for cwd=/ and cwd=/tmp/nvim.XXXXX, to make sure that we
don't have regressions in cwd handling.
Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
vim-patch:7.4.1223
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Crash when setting v:errors to a number.
Solution: Free the typval without assuming its type. (Yasuhiro Matsumoto)
https://github.com/vim/vim/commit/a542c680a8b42cb766e64d4ee7374ef4dacb7832
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Sort test doesn't test with "1" argument.
Solution: Also test ignore-case sorting. (Yasuhiro Matsumoto)
https://github.com/vim/vim/commit/51d1d536802b5d8232d47e56f165ba8a009529b5
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: When the argument of sort() is zero or empty it fails.
Solution: Make zero work as documented. (suggested by Yasuhiro Matsumoto)
https://github.com/vim/vim/commit/5131c144feb046c5e2b72e6c172159d80ce06b3c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Sort test fails on MS-Windows.
Solution: Correct the compare function.
https://github.com/vim/vim/commit/0bb6108eb4e1ecaed437bc507f514f5da7816d9e
|