| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
When set to false, nvim will send cterm color numbers with `highlight_set`.
|
| |
|
|
|
| |
Ignoring invalid key sequences simplifies input handling in UIs. The only
downside is having to use "<lt>" everytime a "<" is needed on functional tests.
|
| | |
|
| | |
|
| |
|
|
|
| |
It is necessary to notify the UI when the default background/foreground colors
change in order to render correctly.
|
| |
|
|
| |
These functions need to operate on the current the scroll region.
|
| | |
|
| |
|
|
|
|
| |
- Remove suspend method from the UI protocol
- Handle `:suspend` by disconnecting the last channel that sent a request to
nvim.
|
| |
|
|
| |
When set to false, nvim will send cterm color numbers with `highlight_set`.
|
| |
|
|
|
| |
Ignoring invalid key sequences simplifies input handling in UIs. The only
downside is having to use "<lt>" everytime a "<" is needed on functional tests.
|
| | |
|
| | |
|
| |
|
|
|
| |
It is necessary to notify the UI when the default background/foreground colors
change in order to render correctly.
|
| |
|
|
|
| |
It should only clear to the end of the current scroll region(this is the
behavior expected by nvim)
|
| |\
| |
| | |
vim-patch:7.4.552
|
| | |
| |
| |
| |
| |
| |
| | |
Problem: Langmap applies to Insert mode expression mappings.
Solution: Check for Insert mode. (Daniel Hahler)
https://code.google.com/p/vim/source/detail?r=v7-4-552
|
| |\ \
| | |
| | | |
vim-patch:7.4.549
|
| | |/
| |
| |
| |
| |
| | |
Add new files for 7.4.549.
https://code.google.com/p/vim/source/detail?r=750a6986aa86a2bb3346631a353913b899d86748
|
| |/
|
|
| |
https://code.google.com/p/vim/source/detail?r=6a598be6d4e8
|
| |
|
|
|
|
|
| |
Problem: test_mapping fails for some people.
Solution: Set the 'encoding' option. (Ken Takata)
https://code.google.com/p/vim/source/detail?r=v7-4-488
|
| |
|
|
|
|
|
| |
Problem: A 0x80 byte is not handled correctly in abbreviations.
Solution: Unescape special characters. Add a test. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-483
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Add screen.lua which implements a remote screen to verify screen state by
tests under functional/ui
- Add some basic screen/highlight tests
|
| | |
|
| | |
|
| |\
| |
| | |
Api: Improve Nul handling
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Remove `expandtab` and add a missing trailing space from the legacy test.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
| |
Move general initialization functions to early_init, which simplifies
test/unit/helpers.lua, which requires all these functions.
|
| |
|
|
| |
- tests for vim_feedkeys and replace_termcodes
|
| |
|
|
|
|
|
| |
While we're at, using the slightly more portable `command -v` technique
to detect the executable. Also, there's no need to use `io.popen()` if
we aren't going to record the path. Instead, let's use the simpler
`os.execute()` to detect the presence of xclip.
|
| |\
| |
| | |
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.
|
| |/
|
|
|
| |
The new version fixes defunct processes which causes random test failures on
some systems(#1519)
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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"
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
