Problem: Using :s with 'incsearch' prevents CTRL-R CTRL-W. (Boris Staletic)
Solution: When past the pattern put cursor back in the start position.
(closesvim/vim#3413)
99f043a57d
Problem: Too much 'incsearch' highlight for pattern matching everything.
Solution: Add the skiplen to the command and remove the line range.
(Christian Brabandt) Check for empty pattern earlier.
8b0d5ce881
Problem: No 'incsearch' highlighting for :vimgrep and similar commands.
Solution: Parse the :vimgrep command and similar ones to locate the search
pattern. (Hirohito Higashi, closesvim/vim#3344)
264cf5cfaf
Problem: 'incsearch' highlighting wrong in a few cases.
Solution: Fix using last search pattern. Restore highlighting when changing
command. (issue vim/vim#3321)
c7f08b7ee1
Problem: 'incsearch' with :s doesn't start at cursor line.
Solution: Set cursor before parsing address. (closesvim/vim#3318)
Also accept a match at the start of the first line.
976b847f43
This will significantly reduce the parsing work
needed e.g. when rehighlighting after every keypress
in insert mode.
Also add safety check for tree-sitter trying to read
past the end of a line. This can happen after we sent
an incorrect buffer update.
Seems like redundant env var separators (";" on Windows) in $PATH can
cause weird behavior. From #7377:
> After some time, system(['win32yank', '-o']) and system('win32yank -o')
> start returning different results: specifically first returns an
> empty string.
>
> 1. $PATH weirdly contains double semicolon followed by path to the
> “installation directory” (unpacked directory from archive).
> 2. If I run `let $PATH=substitute($PATH, ';;', ';', 'g')` the problem is fixed.
close#7377
ref 224f99b85d
- Windows environment variables are semicolon-separated, but some logic
was assuming colon (:). This broke initialization and parsing of
XDG_CONFIG_DIRS, XDG_DATA_DIRS, 'runtimepath', stdpath(), etc.
- test/defaults_spec: enable tests on Windows
ref #12793
Problem: Some error messages are internal but do not use iemsg().
Solution: Use iemsg(). (Dominique Pellé, closesvim/vim#6894)
e83cca2911
N/A patches for version.c:
vim-patch:8.2.1625: compiler warning for use of fptr_T
Problem: Compiler warning for use of fptr_T.
Solution: Make the type less strict.
30d6413782
vim-patch:8.2.1630: terminal test fails
Problem: Terminal test fails.
Solution: Correct argument to term_start(). Correct error number.
c98cdb3bc9
vim-patch:8.1.0113: compiler warning for unused variable
vim-patch:8.1.0294: MS-Windows: sometimes uses short directory name
vim-patch:8.1.0297: MS-Windows: tests fail, Vim crashes
vim-patch:8.1.0338: MS-Windows: VTP doesn't work properly with Powershell
vim-patch:8.1.0718: a couple compiler warnings
vim-patch:8.1.0912: MS-Windows: warning for signed/unsigned
vim-patch:8.1.1130: MS-Windows: warning for unused variable
vim-patch:8.1.1219: not checking for NULL return from alloc()
vim-patch:8.1.1487: older msgfmt cannot generate proper .desktop file
vim-patch:8.1.1528: popup_any_visible() is unused
vim-patch:8.1.2252: compiler warning for int size
vim-patch:8.1.2323: Old MSVC version no longer tested.
vim-patch:8.1.2424: MS-Windows: console buffer is resized unnecessarily
vim-patch:8.2.0541: Travis CI does not give compiler warnings
vim-patch:8.2.0545: unused arguments ignored in non-standard way
vim-patch:8.2.0550: some changes in the libvterm upstream code
vim-patch:8.2.0553: error for unused argument
vim-patch:8.2.0608: warning from clang when building message test
vim-patch:8.2.0781: compiler warning for not using value in Lua
vim-patch:8.2.0838: MS-Windows: compiler warning for uninitialized variables
vim-patch:8.2.0891: clang warns for invalid conversion
vim-patch:8.2.1234: Lua build problem with old compiler
vim-patch:8.2.1487: Travis: installing snd-dummy is not always useful
vim-patch:8.2.1495: "make clean" may delete too many files
vim-patch:8.2.1545: ch_logfile() is unclear about closing when forking
vim-patch:8.2.1546: build rule for Vim.app is unused
vim-patch:8.2.1559: s390x tests work again
vim-patch:8.2.1567: no example to use ubsan with clang
vim-patch:8.2.1579: reports from asan are not optimal
vim-patch:8.2.1583: MS-Windows: cannot easily measure code coverage
vim-patch:8.2.1589: term_start() options for size are overruled by 'termwinsize'
vim-patch:8.2.1594: pull requests on github do not notify a maintainer
vim-patch:8.2.1595: cannot easily see what Vim sends to the terminal
vim-patch:8.2.1596: using win_screenpos('.') in tests works but is wrong
vim-patch:8.2.1598: starting a hidden terminal resizes the current window
vim-patch:8.2.1605: default maintainer on github is wrong
When in ext_multigrid mode, after a window gets resized neovim wont
currently send all the needed events fill the window's blank space and
thus' UIs will have invalid grid state.
* support for :perl, :perlfile, :perldo and perleval()
* document that the perl provider doesn't currently work on Windows
* document that the perl legacy interface is now also supported
* added perleval() documentation
* import legacy perl interface tests
* only perl 5.22+ is supported
* healtcheck: use g:perl_host_prog if its set instead
using just 'perl' isn't correct as it may not be the version requested.
ditto for 'cpanm', rather go through 'App::cpanminus' to find the latest
perl version
UBSAN with clang 10.0 is checking for adding offsets to a `NULL` pointer
which is not allowed. This is not yet checked in the version of clang
used in CI (7.0.0). I will work on cases of this so that tests passes
locally for me.
This could be tested in CI by either upgrading the clang of the
ASAN/UBSAN to 10.0, or add yet another CI target which builds with
clang 10.0.
When running in CI, we want to find as many problems as possible
instead. Let the code try to keep running from recoverable issues so we
report all the sanitize issues we can.
