| Commit message (Collapse) | Author | Age |
... | |
| |/ / |
|
| | | |
|
|\ \ \
| | | |
| | | | |
decoration: Clean up duplicate Decoration attributes + bonus hl_eol flag
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The rpc layer normalizes `vim.NIL` to `nil`, so the scenario tested
should never happen.
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There were a couple of reports of "Buffer X newer than edits" problems.
We first assumed that it is incorrect for a server to send 0 as a
version - and stated that they should send a `null` instead, given that
in the specification the `textDocument` of a `TextDocumentEdit` is a
`OptionalVersionedTextDocumentIdentifier`.
But it turns out that this was a change in 3.16, and in 3.15 and earlier
versions of the specification it was a `VersionedTextDocumentIdentifier`
and language servers didn't have a better option than sending `0` if
they don't keep track of the version numbers.
So this changes the version check to always accept `0` values.
See
- https://github.com/neovim/neovim/issues/12970
- https://github.com/neovim/neovim/issues/14256
- https://github.com/haskell/haskell-language-server/pull/1727
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
nvim-treesitter/feature/language-tree-directive-config
feat(treesitter): allow injections to be configured through directives
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
extmark: splice extmarks on :luado
|
| |/ / / |
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
It looks solid with the default `FloatBorder` group.
If you set the bgcolor of FloatBorder to the same color as for FloatNormal, you
effectively get an "1-cell padding".
|
| | | |
|
|\ \ \
| | | |
| | | | |
extmark: correct extmark_splice call with substitute and inccommand when replacing with escaped backslashes
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Some small cleanups/diagnostic improvements
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Replacement for Vim's test_null_string().
Vim uses it to verify that its codebase handles null strings.
Preparation for the Test_null_list() in patch v8.2.1822.
Use v:_null_string, not non-existent env var, for null string tests.
Mention v:_null_string in id() because id(v:_null_string) returns (nil).
|
|\ \ \
| | | |
| | | | |
feat: treesitter checkhealth
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Border: allow to enable/disable specific border edges
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
api: fix use-after-free in nvim_chan_send
|
| | | | | | |
|
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(#14286)
Problem: Highlighting for :s wrong when using different separator.
Solution: Use separat argument for search direction and separator. (Rob
Pilling, closes vim/vim#5665)
https://github.com/vim/vim/commit/c036e87bd7001238ab7cc5d9e30e59bbf989a5fd
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
extmark: buffer update fixes for `noexpandtab` and `:retab`
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | | |
screen: fix problem with p_ch
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
When the screen is resized, p_ch is not re-set to the appropriate value.
As a result, access to invalid addresses was occurring.
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
dylanarmstrong/fix/13955-empty-paste-in-term-segfault
fix: segfault when pasting in term with empty buffer
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Status line is not updated when going to cmdline mode.
Solution: Redraw status lines if 'statusline' is set and going to status
line mode. (based on patch from Justin M. Keyes et al.,
closes vim/vim#8044)
https://github.com/vim/vim/commit/ce0b75711afb3ff260967a0843bca46ec09604b5
|
|\ \ \
| | | |
| | | | |
Fix dictwatcherdel crash
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Fixes https://github.com/neovim/neovim/issues/11188.
|
| | | | |
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
Make sure that oldwin is not invalid after splitting
Revisit this when porting vim patch v8.1.0892 and related quickfix patches.
|
|\ \ \
| | | |
| | | | |
vim-patch:8.1.{0105,0114,0116,0126,0138,0154,0479,0542,0936}
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Problem: All tab stops are the same.
Solution: Add the variable tabstop feature. (Christian Brabandt,
closes vim/vim#2711)
https://github.com/vim/vim/commit/04958cbaf25eea27eceedaa987adfb354ad5f7fd
|
|\ \ \
| |/ /
|/| | |
api: add vim.api.nvim_win_hide
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Extmarks: send correct buffer events on blockwise paste for nonuniform lines
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
memory error with ephemeral virt_text
|