| Commit message (Collapse) | Author | Age |
... | |
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reference: https://github.com/neovim/neovim/issues/3772#issuecomment-162334005
|
| |/ / /
|/| | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| | | | |
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Recognizing <sid> does not work when the language is Turkish.
(Christian Brabandt)
Solution: Use MB_STNICMP() instead of STNICMP().
https://github.com/vim/vim/commit/e266d6d664d6d743c79797af400b2c01ec746216
Note: Added new test
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: When using packages an "after" directory cannot be used.
Solution: Add the "after" directory of the package to 'runtimepath' if it
exists.
https://github.com/vim/vim/commit/a57024453115592b8847af40ddd965a33898e390
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: For plugins in packages, plugin authors need to take care of all
dependencies.
Solution: When loading "start" packages and for :packloadall, first add all
directories to 'runtimepath' before sourcing plugins.
https://github.com/vim/vim/commit/49b27326447d0827c59c6cd201d58f65c1163086
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Completion for :colorscheme does not use 'packpath'.
Solution: Make it work, add a test. (Hirohito Higashi)
https://github.com/vim/vim/commit/52f9c19015df5ee1ee8592b6f3f15b8a57c8f5be
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: ":runtime" does not use 'packpath'.
Solution: Add "what" argument.
https://github.com/vim/vim/commit/8dcf259d904cfb965d31841dc74a5cfaf5a351d9
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: ":colorscheme" does not use 'packpath'.
Solution: Also use in "start" and "opt" directories in 'packpath'.
https://github.com/vim/vim/commit/7f8989dd8a627af2185df381195351a913f3777f
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Cannot generate help tags in all doc directories.
Solution: Make ":helptags ALL" work.
https://github.com/vim/vim/commit/6bef5306e4f2cacb3a93667992c2312d4b293c9d
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Cannot load packages early.
Solution: Add the ":packloadall" command.
https://github.com/vim/vim/commit/2d8f56acb32428d0f965d42dd13b27100b46fa15
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: No error message when :packadd does not find anything.
Solution: Add an error message. (Hirohito Higashi)
https://github.com/vim/vim/commit/be82c254862e475a582c0717455e1db6bf96b0d0
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: No command line completion for ":packadd".
Solution: Implement completion. (Hirohito Higashi)
https://github.com/vim/vim/commit/35ca0e7a1cb6e6daef8e0052a8437801226cef19
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: ":loadplugin" is not optimal, some people find it confusing.
Solution: Only use ":packadd" with an optional "!".
https://github.com/vim/vim/commit/f3654827368e6204608036353a0360e9e7c21e02
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Cannot add a pack direcory without loading a plugin.
Solution: Add the :packadd command.
https://github.com/vim/vim/commit/91715873d19a1859c08eeded7848113596e2f2bd
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: No testfor ":loadplugin".
Solution: Add a test. Fix how option is being set.
https://github.com/vim/vim/commit/863c1a9079fa340d663ccafb011729a29186d73e
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: test_expand fails on MS-Windows.
Solution: Always use forward slashes. Remove references to test27.
https://github.com/vim/vim/commit/f60b796fa9870bdfc4cdeb91653bac041916077d
|
| | | | |
| | | | |
| | | | | |
Also skip TERM=screen (GNU, so probably not common on BSD)
|
| | | | | |
|
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| |
| |
| |
| | |
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.
|
| | | | |
|