| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This is the part of the test that relies on wall clock time and sometimes
fails if the system is under load. The test is repeated up to three times
before a failure is reported to the user.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
:undojoin can only be used inside scripts and command chains. So it has to be
tested inside an explicit `source()` call.
Also add a new test case for the different behavior when sourceing normal mode
commands from a script or inserting them interactively.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The legacy test uses `set ul=100` to break the changes into blocks that can be
undone separately. This is needed because the legacy test is sourced from a
file and changes would be grouped into on undo block by default. The lua test
suite does not have this restriction.
Also add a new test case to test this effect of using `set ul=100` in a
sourced script.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test is real time based as it also tests the `:earlier` and `:later`
commands with time arguments (using `:sleep`). This can sometimes case the
test to fail on systems that are under heavy load or where the time interval
between creating the expected buffer state and the `:earlier` or `:later`
command that tries to jump to it changes.
To be system independent we use nvim's `:sleep` command and `wait()` for it in
the test suit.
The legacy vim test writes to test.out a lot with `:.w >>test.out`. This
does currently not work in the lua test suite so the test is modernized to use
busted's assertions instead of the output file.
This test was treated special in the legacy Makefile but after the conversion
the related code can be removed.
|
|
|
|
| |
Closes #2791
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
| |
|
|
|
|
|
|
| |
Also update the documentation regarding the option.
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
|
|
| |
This also updates the documentation about 'incsearch'.
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
|
|
| |
"i" could slow down the completion.
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
Also, some documentation changes.
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
|
|
|
| |
Re: https://github.com/neovim/neovim/issues/2676
|
| |
|
|
|
|
|
| |
v:completed_item should always be a dict (not empty string), even before
the first completion.
|
|
|
|
|
|
|
|
|
|
| |
```
updated for version 7.4.575
Problem: Unicode character properties are outdated.
Solution: Update the tables with the latest version.
```
https://code.google.com/p/vim/source/detail?r=v7-4-575
|
|\ |
|
| | |
|
|/ |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
Closes #2779
|
|
|
|
|
|
|
| |
Problem: Overflow when adding MAXCOL to a pointer.
Solution: Subtract pointers instead. (James McCoy)
https://github.com/vim/vim/commit/v7-4-719
|
|
|
|
|
|
|
|
|
|
| |
Problem: Crash when searching for "x\{0,90000}". (Dominique Pelle)
Solution: Bail out from the NFA engine when the max limit is much higher
than the min limit.
https://github.com/vim/vim/commit/v7-4-593
See https://groups.google.com/d/msg/vim_dev/c7owwoseba8/ZETgSNZ6p10J
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
patch 7.4.713
Problem: Wrong condition for #ifdef.
Solution: Change USR_EXRC_FILE2 to USR_VIMRC_FILE2. (Mikael Fourrier)
https://code.google.com/p/vim/source/detail?r=v7-4-713
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These patches are not applicable (NA):
.611 (if_python3.c)
.627 (term.c)
.666 (X on *nix)
.678 (--remote)
.683 (vimtutor)
.687 (terminal)
.691 (mzscheme)
.692 (Solaris)
.730 (crypto)
.731 (GUI)
.738 (compiling w/o syntax highlighting)
.644 applied in an unsupported platform (Stratus VOS)
|
| |
|
|\ |
|
| |
| |
| |
| | |
074_global_var_in_viminfo_spec: remove some redundant sanity checks.
|
| | |
|
|/
|
|
|
| |
Helped-By: David Bürgin <676c7473@gmail.com>
Helped-By: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
|
|
|
|
| |
When ml_add_stack() needs to increase the size of the empty stack,
buf->b_ml.ml_stack is NULL and is used as argument in memmove().
This is undefined behaviour. Declaration of memmove() in string.h:
extern void *memmove (void *__dest, const void *__src, size_t __n)
__THROW __nonnull ((1, 2));
|
| |
|
|\
| |
| |
| | |
interpreter for +python, improve messages'.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The executable 'python' can refer to either Python 2 or Python 3. Add a
check to only accept Python 2 interpreters as providers for +python.
Also improve the error messages.
Resolves #2734.
|
| |
| |
| |
| | |
Ref: https://github.com/blueyed/neovim/commit/9b653ce0#commitcomment-11195449
|