| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
This is the result of malloc error handling elimination: push_current_state()
used to (not) return OK depending on whether growing garray failed or not and
this return was checked, if errorred out push_next_match() will simply return
its argument unchanged.
Now when allocations are supposed to either always succeed or crash Neovim this
check was returned, push_current_state() was stripped of its return value and
moved out of if() condition, resulting in V763.
|
| |
|
| |
|
|
|
|
| |
The code uses 2-iteration loop antipattern: retval is NULL on first iteration,
not NULL on second, yet this is still a false positive.
|
| |
|
|
|
|
| |
Apparently the latter is not a part of the public C API.
|
| |
|
|
|
|
| |
Code imported from #6299
|
| |
|
|
|
|
|
| |
It is useless to use sbuffer here and print that to stdout, just using “fbuffer”
instead.
|
|
|
| |
This is usual “passing data via global” false positive.
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes #6937
|
| | |
|
| |
| |
| | |
Apparently it is not working yet.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Does not alter its usages.
|
| |
| |
| |
| | |
Does not alter their usages as well.
|
| |
| |
| |
| | |
Does not alter its usages.
|
| | |
|
|\ \
| |/
|/| |
test: expand_env_esc: Pass correct buffer size for outlen and assertion
|
|/
|
|
|
|
|
|
| |
Running this test with a mocked passwd file whose $HOME was set to
/home/jamessan/src/debian.org/pkg-vim/deb-packages/neovim/neovim-0.2.0/debian/fakehome
caused the test to fail, since the expanded result was >= 99 bytes. The
test should be reflecting the actual size of the buffer, instead of some
arbitrary other number, anwyay.
|
|
|
|
|
|
|
|
| |
Temporarily disable this test which hangs quickbuild.
From #6905: The hang occurs when calling nvim_set_current_line.
References #6594 5a151555c8dce70bbf235e7f6d5bd1ced5e7c46c
|
| |
|
|\
| |
| | |
Update to Unicode 10
|
| | |
|
| | |
|
|/
|
|
| |
vim-patch:8.0.0652
|
|
|
|
|
|
|
|
| |
The main purpose of this build-type was to avoid unwanted ~/.nvimlog
files (which could get really big, and also affects performance) for
non-devs. But that is no longer necessary since the log system now
avoids non-critical logging by default (#6827).
This essentially reverts 87e5a4131666e44354f280538cbc6bbe52225092
|
| |
|
|
|
|
| |
Closes #6029
|
|\
| |
| | |
vim-patch:7.4.2259,7.4.2268,7.4.2318,7.4.2320
|
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | | |
lua: Add paths from &runtimepath to package.path and package.cpath
|
| | | |
|
| | | |
|