- TUI: Fix a case where the cursor was not displayed after hiding the
cursor and then setting it to be displayed again.
- Change to reset everything before setting guicursor.
fixes#12800close#12811
Steps to reproduce:
nvim -u NORC
:set termguicolors
:hi nCursor guifg=red guibg=red
:hi iCursor guifg=green guibg=green
:hi cCursor guifg=blue guibg=blue
:set guicursor=n:block-nCursor,i:hor25-iCursor,c:ver25-cCursor
:set guicursor-=c:ver25-cCursor
Actual behaviour: Cursor is a blue vertical.
Expected behaviour: Cursor should be the default color block.
* docs: Add hint for :help vim.lsp.buf for new users
* fix: Use help linker for vim.lsp.buf
* docs: Extend full api list language. Move gd to bottom. Add note about limited support
Problem: Invalid argument test fails without X clipboard.
Solution: Test -display only with the +xterm_clipboard feature.
5416b75031
N/A patches for version.c:
vim-patch:8.2.1640: Amiga: missing header for getgrgid()
Problem: Amiga: missing header for getgrgid().
Solution: Add the grp.h header. (Ola Söder, closesvim/vim#6906)
f842cd9e28
vim-patch:8.2.1645: GTK3: icons become broken images when resized
Problem: GTK3: icons become broken images when resized.
Solution: Use gtk_image_new_from_icon_name(). (closesvim/vim#6916)
Fix compiler warnings.
81a4cf469a
vim-patch:8.2.1646: Amiga: Unnecessary #include
Problem: Amiga: Unnecessary #include.
Solution: Remove the #include. (Ola Söder, closesvim/vim#6908)
33e3346322
vim-patch:8.2.1648: Amiga: no common build file for Amiga (-like) systems
Problem: Amiga: no common build file for Amiga (-like) systems.
Solution: Turn Make_morph.mak into Make_ami.mak. (Ola Söder, closesvim/vim#6805)
a62372be1f
vim-patch:8.2.1649: GTK3: using old file chooser
Problem: GTK3: using old file chooser.
Solution: Use native file chooser on GTK 3.20 and above. (Yogeshwar
Velingker, closesvim/vim#6909)
3e4cc9671c
vim-patch:8.2.1654: when job writes to hidden buffer current window is wrong
Problem: When job writes to hidden buffer current window has display
errors. (Johnny McArthur)
Solution: Use aucmd_prepbuf() instead of switch_to_win_for_buf().
(closesvim/vim#6925)
ad9ec5e799
vim-patch:8.2.1655: cannot build with Strawberry Perl 5.32.0
Problem: Cannot build with Strawberry Perl 5.32.0.
Solution: Use Perl_sv_2pvbyte_flags. (closesvim/vim#6921)
895a7a472d
vim-patch:8.2.1661: cannot connect to 127.0.0.1 for host with only IPv6 addresses
Problem: Cannot connect to 127.0.0.1 for host with only IPv6 addresses.
Solution: pass AI_V4MAPPED flag to getaddrinfo. (Filipe Brandenburger,
closesvim/vim#6931)
c6a67c92bc
Problem: Saved last search pattern may not be restored.
Solution: Call restore_last_search_pattern(). Add a check for balancing
saving and restoring the last search pattern.
01a060da74
Problem: 'hlsearch' highlight remains in other window after cancelling
command.
Solution: Redraw all windows. Also remove unnecessary delays. (closesvim/vim#3437)
65985ac998
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.
