| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | | |
Helped-by: Justin M. Keyes <justinkz@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
The old test_eval.in file did a `:wq` on line 168. The following 60 lines
where not used and there was no expected output for them in test_eval.ok.
This test code is now used in several test cases in the new test file.
|
| | | |
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Illegal memory access when using :copen and :cclose.
Solution: Avoid that curbuf is invalid. (suggestion by Justin M. Keyes)
Add a test.
https://github.com/vim/vim/commit/62ef797496c6243d111c596a592a8ef8c1d1e710
|
|\ \
| |/
|/| |
coverity/125476: RI: Null pointer dereference
|
| | |
|
| | |
|
| |
| |
| |
| | |
https://github.com/vim/vim/commit/ac80999985299dae4a9ef56dbf31fbdb35c04c08
|
| |
| |
| |
| | |
If nvim was compiled without `has("iconv")` this test is skipped.
|
|/ |
|
|
|
|
|
|
| |
Add test files for patch 7.4.680.
https://github.com/vim/vim/commit/dbcf19dc498cb1561c9215a3f255e81cde0c0543
|
|\
| |
| | |
vim-patch:7.4.729
|
| |
| |
| |
| |
| |
| | |
This is consistent with VIM behavior. When showing a visual selection,
VIM only extends it past the last character if eol is in listchars (even
if nolist is set).
|
|\ \
| | |
| | | |
vim-patch:7.4.616
|
| |/ |
|
| |
| |
| |
| |
| | |
before_each(clear) is required to init the test harness for single-test
runs, and also to ensure a known environment for each test.
|
|\ \ |
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | | |
Vim 7.4.9{78,80,81,91}
|
| |/ |
|
|/
|
|
|
|
|
|
|
|
| |
Although UNIX is a registered trademark of The Open Group, it doesn't
really matter whether we refer to these systems as UNIX, Unix, or
Unix-like. So, for consistency, refer to them collectively as Unix.
Related:
http://www.greens.org/about/unix.html
http://www.unixica.com/html/unixunix.html
|
|
|
|
|
|
|
|
|
| |
POSIX.1-2008[1] says that the latter should be used, and all of our
supported platforms would seem to support this scheme, apparently even
Windows[2].
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/fcntl.h.html
[2]: https://msdn.microsoft.com/en-us/library/z0kc8e3z.aspx
|
|
|
|
|
|
|
| |
Problem: There is no test for what patch 7.4.601 fixes.
Solution: Add a test. (Christian Brabandt)
https://github.com/vim/vim/commit/d7ce7a9ad2d9311f7ec3368eeddec8fce6d8e890
|
|
|
|
|
| |
process_interrupts() checks get_real_state() so we can avoid some
housekeeping of mapped_ctrl_c in terminal-mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
vim-patch:7.4.569
vim-patch:7.4.573
Helped-by: @glts https://github.com/neovim/neovim/pull/2621
Problem: Having CTRL-C interrupt or not does not check the mode of the
mapping. (Ingo Karkat)
Solution: Use a bitmask with the map mode. (Christian Brabandt)
https://github.com/vim/vim/commit/651863c94a882a97aec7968fc87a638ff78e56ff
Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat)
Solution: Call get_real_state() instead of using State directly.
https://github.com/vim/vim/commit/5000869712f799d9ca25c0e45dc21d332edae5f4
|
|\
| |
| | |
input: Do not set high-bit. Preserve META modifier.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Background: Vim internally prefers to represent ALT/META chords as
single-byte keys, by setting the high bit of the key byte.
extract_modifiers() _discards_ the meta/alt modifier, but we need it for
libvterm and libtermkey.
Closes #2440
Closes #3727
Closes #2017
References #2277
References #2254
https://github.com/neovim/neovim/issues/2017#issuecomment-140423557
> We [not libtermkey] are setting the high bit for some reason
https://github.com/neovim/neovim/issues/176#issuecomment-77834715
> libvtermkey requires the leading esc to parse alt/meta
https://github.com/neovim/neovim/pull/3246#issuecomment-136328450
> A program could do better than the current logic on some terminals, by
> asking for pure 8bit mode (S8C1T) and then immediately querying the
> mode again. If the result comes back as an 8bit single-byte CSI, then
> it can presume the mode setting was successful, and now the ESC prefix
> byte won't be seen in multibyte sequences; only as an Alt- prefix or
> a real Escape key. On such a terminal, it could therefore avoid
> needing to use that waiting timeout.
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Travis defines[1] $CI for its builds, whereas $CI_TARGET is
a Neovim-specific env var from 6483a198e4bee1e80683ba12e061616c3e6c4090
that lost prominence in d2eb4a934683b5da63000d8b79a0d4c9a314d1c0.
[1] https://docs.travis-ci.com/user/environment-variables/
|
|
|
|
|
| |
On Windows the default file format is DOS i.e. newlines are \r\n
instead of \n.
|
| |
|
|\
| |
| | |
helpers.c: Handle msgpack str/bin objects with length 0 correctly
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When converting a msgpack object to a String object, strings (and byte
arrays) with length 0 are handled as errors. This is fixed by
always using the msgpack data pointer as a valid pointer. For a NULL
pointer there is nothing to copy.
Test by @snoe
Fixes #3844
|
|/ |
|
|\
| |
| | |
shada: Continue dumping when variables failed to dump
|
| |
| |
| |
| | |
Closes #3721
|
| |
| |
| |
| |
| |
| |
| | |
Problem: C indent does not support C11 raw strings. (Mark Lodato)
Solution: Do not change indent inside the raw string.
https://github.com/vim/vim/commit/f7bb86dc593913d055e4cce16cec43f6271adda3
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Using 'cindent' for Javascript is less than perfect.
Solution: Improve indenting of continuation lines. (Hirohito Higashi)
https://github.com/vim/vim/commit/dcefba993456263100785f18d21d780cf531f2dc
|