| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Vim "unix default" of 'noshowcmd' is serving few users. And it's
inconsistent.
- 'ruler' and 'belloff=all' improve the out-of-the-box experience.
- Continue to use 'noshowcmd' and 'noruler' by default in the functional
tests to keep them fast.
TODO: Add a "disable slow stuff" command or mapping to address the
use-case of a very slow terminal connection.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After using 'termopen("echo") the current buffer content is changed,
but the cursor position of the current window is not updated.
Because of this, a call to 'mb_adjust_cursor()' can lead to a
heap-buffer-overflow.
Fix this by resetting the cursor for the current window.
Fixes #3161
|
| |
| |
| |
| |
| |
| | |
Let the terminal dictate the normal-mode cursor position. This will be
disorienting sometimes, but it is closer to what users expect vs always
going to the last line.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Make the test work after the "follows cursor" changes.
This "auto-resize" feature is going away soon, anyways.
|
| |
| |
| |
| |
| |
| | |
Closes #2257
Closes #2636
References #2683
|
| |
| |
| |
| | |
Closes #2637
|
| | |
|
| |
| |
| |
| | |
Closes #4299
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Periodically skip :! spam. This is a "cheat" that works for all UIs and greatly
improves responsiveness when :! spams MB or GB of output:
:!yes
:!while true; do date; done
:!git grep ''
:grep -r '' *
After ~10KB of data is seen from a single :! invocation, output will be skipped
for ~1s and three dots "..." will pulse in the bottom-left. Thereafter the
behavior alternates at every:
* 10KB received
* ~1s throttled
This also avoids out-of-memory which could happen with large :! outputs.
Note: This commit does not change the behavior of execute(':!foo').
execute(':!foo') returns the string ':!foo^M', it captures *only* Vim
messages, *not* shell command output. Vim behaves the same way.
Use system('foo') for capturing shell command output.
Closes #1234
Helped-by: oni-link <knil.ino@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/mpeterv/luacheck/pull/81#issuecomment-261099606
> If you really want to use bleeding-edge version you should get the
> rockspec from master branch, not a fixed commit ...
> The correct way to install from a specific commit is cloning that
> commit and running "luarocks make" from project directory. The reason
> is that running "install" or "build" on an scm rockspec fetches
> sources from master but uses build description from the rockspec
> itself, which may be outdated.
|
| | |
|
| |
| |
| |
| | |
References #2748
|
| |
| |
| |
| |
| | |
Previously, the nvim_input from the socket channels could be processed
before the input from stdin in rare cases.
|
| |
| |
| |
| | |
References #5455
|
| |
| |
| |
| |
| |
| | |
References #5445
See https://github.com/neovim/neovim/pull/5445#issuecomment-252529766
|
| |
| |
| |
| |
| | |
This is an (unsuccessful) attempt to cover #4163.
It covers other behavior, so it's worth keeping.
|
| |
| |
| |
| |
| | |
- Behavior changed in 7.4.1547
- Also removed N/A specs: nvim does not support ":hi term=..."
|
| |
| |
| |
| | |
Refresh colors if changing Normal group
|
|\ \
| | |
| | | |
Enable functional tests in Appveyor
|
| | | |
|
|/ /
| |
| |
| | |
update screen.lua to use new style nvim_ui_attach
|
|/ |
|
|
|
| |
Also skip TERM=screen (GNU, so probably not common on BSD)
|
| |
|
| |
|
| |
|
|
|
|
| |
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
|
|
|
|
|
|
| |
It is otherwise impossible to determine which test failed sanitizer/valgrind
check. test/functional/helpers.lua module return was changed so that tests which
do not provide after_each function to get new check will automatically fail.
|
| |
|
|
|
|
| |
References #4393
|
|
|
|
| |
Closes #4554
|
|
|
|
| |
References #4554
|
|
|
|
|
|
| |
This was not a problem locally, but would often/sometimes/etc. (YMMV) fail on QB
and/or travis. This seems to fix it. Quoting @justinmk: "I have a feeling this
is just a bug in the bracketed paste special-cases in the existing code".
|
| |
|
| |
|
|
|
|
|
|
|
| |
The hexadecimal notation is a Luajit extension which is not compatible with Lua
5.1. While Lua 5.2 does support hexadecimal sequences, it is better to target
Lua 5.1 for maximum compatibility with Luajit(which has fully compatible with
5.1 API/ABI).
|
| |
|
| |
|
| |
|
|
|
|
| |
Ref #4306
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
The focus event tests now live in their own `describe` block with each
test testing the handling of focus events in a single mode.
|