| Commit message (Collapse) | Author | Age |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
add cchar_to_string
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
vim-patch:7.4.1636
Closes #7378
|
|
|
|
| |
Restores behavior from commit: 02e86ef04cc1
|
|
|
|
|
| |
If :echo is done by an timer or event (such as FocusGained/FocusLost),
redrawcmdline() clobbers it.
|
|
|
|
|
| |
closes #4840
closes #6164
|
| |
|
|\ |
|
| |
| |
| |
| | |
False positive. From C:\msys64\mingw64\bin\gcc.exe (appveyor CI)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Unlike the normal wildmenu, the CTRL-D wild-list is not restored by
statusline redraw. (Semantics: ^D is controlled by 'wildoptions' option,
so it's in the "wild..." family.)
TODO: externalize the c_CTRL-D wild-list.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: No completion for ":messages".
Solution: Complete "clear" argument. (Hirohito Higashi)
https://github.com/vim/vim/commit/9e507ca8a3e1535e62de4bd86374b0fcd18ef5b8
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
17:25:45,363 WARN - /home/quickbuild/buildagent/workspace/root/neovim/pull-requests-automated/src/nvim/ex_getln.c: In function ‘color_cmdline’:
17:25:45,363 WARN - /home/quickbuild/buildagent/workspace/root/neovim/pull-requests-automated/src/nvim/ex_getln.c:2335:8: error: variable ‘printed_errmsg’ set but not used [-Werror=unused-but-set-variable]
17:25:45,363 WARN - bool printed_errmsg = false;
17:25:45,363 WARN - ^
17:25:45,399 WARN - cc1: all warnings being treated as errors
|
| | |
|
| |
| |
| |
| | |
Otherwise there will be infinite recursion and shortly a crash. Running
redrawcmdline recursively occurs under color_cmdline_error label.
|
| | |
|
| |
| |
| |
| | |
These are actually needed for two modes only. And even for these modes they
should eventually go away.
|
| |
| |
| |
| |
| |
| |
| | |
The issue with debug mode was actually not cleaning up after `try_enter`:
location `&tstate` was pointing to got invalidated and received some “garbage”
(actually, values that got stored on the stack afterwards). But pointer to that
garbage was still stored in `msg_list`, so next attempt to check it resulted in
a crash.
|
| |
| |
| |
| | |
This fixes memory leak reported by ASAN. This also somehow fixes test40, though
I have no idea why except that that test yields memory leak report.
|
|\| |
|
| |
| |
| | |
This is usual “passing data via global” false positive.
|
| |
| |
| |
| |
| | |
Create new functions to handle moving to the next incsearch match or
matching history index.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Redraw problem when using 'incsearch'.
Solution: Save the current view when deleting characters. (Christian
Brabandt) Fix that the '" mark is set in the wrong position. Don't
change the search start when using BS.
https://github.com/vim/vim/commit/dda933d06c06c2792bd686d059f6ad19191ad30b
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: When 'incsearch' is not set CTRL-T and CTRL-G are not inserted as
before.
Solution: Move vim/vim#ifdef and don't use goto.
https://github.com/vim/vim/commit/349e7d94e6bbb253bb87adad9039f095128ab543
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Using CTRL-N and CTRL-P for incsearch shadows completion keys.
Solution: Use CTRL-T and CTRL-G instead.
https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: With 'incsearch' can only see the next match.
Solution: Make CTRL-N/CTRL-P move to the previous/next match. (Christian
Brabandt)
https://github.com/vim/vim/commit/4d6f32cbfbaf324ac4a25c0206a5db0e9f7a48f7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: when processing cycle such as
:for pat in [' \ze*', ' \zs*']
: try
: let l = matchlist('x x', pat)
: $put ='E888 NOT detected for ' . pat
: catch
: $put ='E888 detected for ' . pat
: endtry
:endfor
`:let l = …` throwing an error causes this error to be caught after
color_cmdline attempts to get callback for highlighting next line (the one with
`$put = 'E888 NOT…`). Saving/restoring state prevents this from happening.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This also attempted to fix problem with cancelling input() on error by avoiding
standard error printing facilities (assumed thrown error message is the
problem), but with no luck so far.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|