| Commit message (Collapse) | Author | Age |
|
|
| |
fix #8428
|
|
|
|
|
| |
Problem: No test for synIDattr() returning "strikethrough".
Solution: Extend the synIDattr() test. (Jaskaran Singh, closes vim/vim#4929)
https://github.com/vim/vim/commit/dcb2b9cb085288d2a2e4cc31abc591ade04e782e
|
|\
| |
| | |
getdigits: introduce `strict`, `def` parameters
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem:
During a refactor long ago, we changed the `getdigits_*` familiy of
functions to abort on overflow. But this is often wrong, because many
of these codepaths are handling user input.
Solution:
Decide at each call-site whether to use "strict" mode.
fix #5555
|
|/ |
|
|
|
|
|
| |
Problem: Too many #ifdefs.
Solution: Always build with the +visualextra feature.
https://github.com/vim/vim/commit/870ba5f6dce974b6c1c47bf9d3b20db805d10b36
|
|
|
|
|
| |
Problem: Possibly using uninitialized memory.
Solution: Check if "dict" is NULL. (closes vim/vim#4925)
https://github.com/vim/vim/commit/dbec74907eb614517bcf27116d5aad32e087f241
|
|
|
|
| |
ref 77594d55f709
|
| |
|
|
|
|
| |
Closes https://github.com/neovim/neovim/issues/10031
|
|
|
|
|
|
| |
fix #3436
Includes:
vim-patch:8.0.1038: strike-through text not supported
|
|\
| |
| | |
vim-patch:8.0.1772,8.1.{248,259,261,267}
|
| |
| |
| |
| |
| |
| | |
Problem: No good check if restoring quickfix list worked.
Solution: Let qf_restore_list() return OK/FAIL. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/90f1e2b7bcf56112e1535b693acf131727179a6e
|
| |
| |
| |
| |
| |
| | |
Problem: Coverity complains about a negative array index.
Solution: When qf_id2nr() cannot find the list then don't set qf_curlist.
https://github.com/vim/vim/commit/38efd1d17a6e6aa2add71efdf2cde4a788e5f5e5
|
| |
| |
| |
| |
| |
| | |
Problem: No test for fixed quickfix issue.
Solution: Add a test. Clean up the code a bit. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/3f347e4716c44cf6458be407e712e3d708d82580
|
| |
| |
| |
| |
| |
| | |
Problem: duplicated quickfix code.
Solution: Move the code to a function.
https://github.com/vim/vim/commit/8d8a65e389cef318ae661ff0fe7b1b00fd7cb25f
|
|/
|
|
|
|
| |
Problem: Quickfix: mixup of FALSE and FAIL, returning -1.
Solution: Use FAIL and INVALID_QFIDX. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/29ce409bfca52bb8a07e2975d06fd788458e9861
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this, --embed UIs (without --headless) would not trigger UIEnter.
For TUI, maybe UIEnter isn't useful, but:
- It is less "surprising"/special.
- Makes documentation simpler.
- When TUI becomes a coprocess, it will happen anyway.
|
| |
| |
| |
| |
| | |
"enter"/"leave" is more conventional for Vim events, and
"attach"/"detach" distinction does not gain much.
|
| |
| |
| |
| |
| | |
Even though it's always zero currently, it's less confusing if all UIs
have the same fields.
|
| |
| |
| |
| |
| | |
doc: ginit.vim, gvimrc
fix #3656
|
|/ |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
* tests: move os_kill to functional helpers
* tests: fix system_spec when run with clipboard manager
Replaces "xclip" with a dedicated helper program.
Fixes: https://github.com/neovim/neovim/issues/4900#issuecomment-501866842
|
|
|
|
|
|
|
|
| |
libvterm now advertises a version number, so we can specify the minimum
required version. And this is necessary because there were breaking
changes in its API.
ref 2a590e229363
ref https://github.com/neovim/neovim/issues/10991
|
|
|
|
|
| |
"Multicast" is perhaps a more conventional name for the concept.
"One-shot" is the conventional name for how the event is (currently)
scheduled.
|
|
|
|
| |
This avoids getting "stuck". If user actually _wants_ to get stuck
forever, they could use `:sleep` or specify a really big `interval`.
|
|\ |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| | |
fix #10127
fix #5972
|
|/ |
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Changes for new VTermColor struct (libvterm 0.1)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
simplify handling of default colors
nvim is always true color internally, remove ui_rgb_attached() check.
Fix "runtime termguicolors" test. The test actually reflected broken behavior
in (parent) nvim: nvim_ui_set_option("rgb", true) was not respected by existing
:terminal instances, so all 16-palette colors became dark blue.
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
(Port some refactoring, but ignore "balloon" changes.)
Problem: Cannot use 'balloonexpr' in a terminal.
Solution: Add 'balloonevalterm' and add code to handle mouse movements in a
terminal. Initial implementation for Unix with GUI.
https://github.com/vim/vim/commit/51b0f3701ecb440aa72ab6017c1df6940c0e0f6f
|
|\
| |
| | |
vim-patch:8.0.{937,941}
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Existing color schemes don't work well with StatusLineTerm.
Solution: Don't use "reverse", use fg and bg colors. Also add
StatusLineTermNC.
https://github.com/vim/vim/commit/05fbfdcda48a564e7a778c67251f732481f3ceaa
|