| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\ \ \ \
| | | | |
| | | | | |
Fix outdated msgpack-rpc doc.
|
| | |/ / /
| | | |
| | | |
| | | | |
Needed after neovim/python-client#58.
|
| |\ \ \ \
| |_|/ /
|/| | | |
build: allow skipping of the hash check in the download step
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is useful when trying to bisect an issue in a dependency, and we
want to pull from a specific commit but don't want to have to download
and determine the sha1sum and md5sum of the tarball.
|
| |\ \ \ \
| | | | |
| | | | | |
Improve Python host messages.
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| |/ / /
|/| | | |
build: probe the compiler to see if we need to turn down _FORTIFY_SOURCE
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
Some builds don't use Release (such as Gentoo, though it can be told
to). So let's go a bit further and probe the compiler to see if we need
to turn down the _FORTIFY_SOURCE level.
|
| |\ \ \
| | | |
| | | | |
build: print the error result when the tests fail
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Any diagnostic information is useful when things fail. In my case, it
printed out the fact that the tests were segfaulting.
|
| |\ \ \ \
| |_|/ /
|/| | | |
Fix broken functional test.
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
In Lua, all math is floating point. We need to coerce the result of a
division into a integer with the `{get,set}_height` and
`{get,set}_width` window_spec functional tests.
|
| |\ \ \
| | | |
| | | | |
add missing refcount increment for systemlist()
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- get_system_output_as_rettv() was missing a refcount increment when
returning an empty list, i.e. when there was no output
- we now use rettv_list_aloc() instead of list_alloc()
- issue #1530
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| |/ / /
| | |
| | |
| | |
| | | |
The new version fixes defunct processes which causes random test failures on
some systems(#1519)
|
| |\ \ \
| | | |
| | | | |
Print an error and exit when there are no plugins.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Issue: #1537
Running the :UpdateRemotePlugins command will show an ugly, unhelpful
error when no plugins were found. This change has neovim print an error message
and does not attempt to start the python-client which requires at least one
plugin.
|
| |\ \ \
| |/ /
|/| | |
Memory functions: Improve style.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
`try_malloc` was changed in 8bb2c2c0742c57150655e18cf8418a758cebdce8 to
avoid a warning when size is 0. Then, this improves some things on that:
- Use local vars instead of changing parameters.
- Homogenize style for other related functions.
|
| |\ \
| | |
| | | |
clipboard: check for X on every invocation
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
xsel and xcopy may be available even if a valid X display is not. Also,
the availability of X may change at any time, so check on each
invocation.
Closes #1509.
|
| |\ \ \ |
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
The $GDB env var can be set to run tests under gdbserver. If $VALGRIND is also
set, it will add the --vgdb=yes command-line option to valgrind instead of
starting gdbserver.
|
| |\ \ \
| |/ /
|/| | |
Fix functional tests failing on OSX.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
See https://github.com/neovim/neovim/issues/1519 for failure report.
Cause : In OSX, /tmp is a symbolic link to /private/tmp, which causes
expected and got results different because of implicit
resolution.
Solution : Resolve path before setting expected value.
|
| |\ \ \
| | | |
| | | | |
Fix Makefile for running valgrind with old tests.
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| | |
Add helper script for porting vim patches.
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Two new functions, `event_enable_deferred()`/`event_disable_deferred()` have to
be called by code that is capable of handling asynchronicity. User-dialog states
like "press ENTER to continue" or the swap file confirmation no longer will
generate K_EVENT.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Nvim wasn't exiting cleanly in some job tests due to errors.
This can't be noticed until the next commit, which will perform a refactoring to
selectively process K_EVENT, so the `qa!` command executed at the end of each
test blocks forever if there are errors which require the user to press ENTER(in
that state Nvim no longer will process events).
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The vim_input function accepts raw terminal input and so is better to emulate
real user, especially because it is not deferred as vim_feedkeys.
Using this function required a number of changes:
- expect() was refactored to use curbuf_contents()
- The vim_eval function in request() was moved to curbuf_contents(). For most
cases this is enough(we only care for synchronizing api calls with user input
when verifying buffer contents).
- <C-@>(NUL) is preprocessed before being passed to replace_termcodes.
- Legacy test 4 had a bug that only became visible when using vim_input, it is
fixed now.
- An extra blank line deletion was required for test 101
The last two items show that vim_feedkeys because it is not 100% equivalent to
receiving terminal input.
|
| |/ / / |
|
| |\ \ \ |
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
- Rename autoload/rpc to autoload/remote
- External plugins are now remote plugins
- External plugins directory is "rplugin"
|
| |\ \ \
| | | |
| | | | |
Fix outdated doc: Connecting to nvim through python REPL.
|
| |/ / /
| | |
| | |
| | |
| | | |
After neovim/python-client@b8b48bbe8fe9ee41ad73c9bd5a45e808504399e2,
docs were no longer relevant.
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
