| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
| |
* doc: Add info about vim dicts in lua
* doc: preamble and info
* doc: remove weird spacing
* fixup
|
| |
|
|
|
|
|
|
| |
If the LSP sends an end line that is larger than what nvim considers to be the
last line, you get an Index out of bounds error when fetching the line from
nvim, a change that was introduced in #12223. This change removes the strict
indexing and checks the return value from nvim_buf_get_lines.
|
| |
|
|
|
|
|
|
| |
Problem: Cannot delete a match from another window. (Paul Jolly)
Solution: Add window ID argument to matchdelete(), clearmatches(),
getmatches() and setmatches(). (Andy Massimino, closes vim/vim#4178)
https://github.com/vim/vim/commit/aff749145e23c0f20b5158d1d3a942948ed138e3
|
|
|
|
|
|
|
| |
At least the `gopls` language server seems to return nil/null if no code
actions are available. Currently this results in an error:
> Error executing vim.schedule lua callback: shared.lua:199: Expected table, got nil
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add textDocument/codeAction
* Add callback for workspace/executeCommand
* Escape newlines in codeAction titles
* Return empty list in get_line_diagnostics if no buffer diagnostics
* Add stub documentation
* Validate context parameter in code_action
* Add support for edit in CodeAction responses
* Group diagnostics by line in vim.lsp.util.get_line_diagnostics()
* Advertise code action literal support
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Problem: Some files not recognized as pamenv.
Solution: Add pam_inv.conf. (closes vim/vim#6065)
https://github.com/vim/vim/commit/aacc6afdb8cdeb2558e6942dcd65ca0079bec1ee
|
| |
| |
| |
| |
| |
| | |
Problem: The pam_environment file is not recognized.
Solution: Add a filetype pattern for pamenv. (closes vim/vim#6051)
https://github.com/vim/vim/commit/611548105394fdb76827cd431230c9fbfed39929
|
| |
| |
| |
| |
| |
| | |
Problem: Indent tests don't run on CI for FreeBSD.
Solution: Set modeline. (Ozaki Kiichi, closes vim/vim#6048)
https://github.com/vim/vim/commit/3657686a0e8fd07428a25c2cf9efcc8b5d33f895
|
| |
| |
| | |
applyEdit is supported by the built-in client.
|
|/ |
|
|
|
|
|
|
|
|
| |
According to the specification workspace/applyEdit needs to respond with
a `ApplyWorkspaceEditResponse`
See https://microsoft.github.io/language-server-protocol/specifications/specification-current/#workspace_applyEdit
This is a subset of https://github.com/neovim/neovim/pull/11607
|
|
|
|
|
|
|
|
|
| |
* runtime/syntax/tutor: fix broken inline spans
Also, conceal the ends of code blocks.
Re: #11401 and #12273
* fixup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Make apply_text_edits non-ASCII safe
Use `vim.str_byteindex` to correct starting and ending positions for text edits if the line contains non-ASCII characters.
Fixes #12221
* text_edit may be applied to other buffers
* make sure the buffer is loaded
* add comments
* add test for non-ASCII edits
|
|
|
|
|
|
|
|
|
|
|
| |
* lsp: handle kinds not specified in protocol
fix: #12200
If the client set "symbolKind.valueSet",
the client must handle it properly even if it receives a value outside the specification.
* test: add lsp.util.{get_completion_item_kind_name, get_symbol_kind_name} test case
* lsp: make lsp.util.{get_completion_item_kind_name, get_symbol_kind_name} private
|
| |
|
|\
| |
| | |
vim-patch:8.1.{800,868,1581},8.2.{648,649,663,678,681,688,691,692}
|
| |
| |
| |
| |
| |
| | |
Problem: Output clobbered if setting 'verbose' to see shell commands.
Solution: Only output "Searching for" when 'verbose' is 11 or higher.
https://github.com/vim/vim/commit/647a530b33d9d767f591159c24c62de48e57dad7
|
| |
| |
| |
| |
| |
| | |
Problem: Not all systemd temp files are recognized.
Solution: Add two more patterns. (Jamie Macdonald, closes vim/vim#6003)
https://github.com/vim/vim/commit/512fe833c3988bfe0de22135aef67faf51927a0e
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Cannot easily get directory entry matches.
Solution: Add the readdir() function. (Yasuhiro Matsumoto, closes vim/vim#2439)
https://github.com/vim/vim/commit/543c9b1921d7605498b54afdef518e312f1b4515
closes #12212
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Besides the special-case in get_scrolloff_value(), it makes sense for
'scrolloff' and 'sidescrolloff' to reflect the correct values (for
plugins, scripts, …).
ref 53d607af9c53accfd634435908fb79061f1212b9
ref #11915
ref #12230
|
| | |
|
| |
| |
| | |
Fixes https://github.com/neovim/neovim/issues/12210
|
| |
| |
| | |
Co-authored-by: BodongLiKolmostar <bodong.li@kolmostar.com>
|
|\ \
| |/
|/| |
lsp: text_document.version may be vim.NIL not nil
|
| | |
|
| |
| |
| | |
use workspace.symbol instead of workspaceSymbol to mimic the lsp spec.
|
|\ \
| | |
| | | |
lsp: fix lsp.util.symbols_to_items with DocumentSymbol has children
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
fix: https://github.com/neovim/neovim/pull/11931#issuecomment-622422581
There was an error in the process of flattening the hierarchical structure.
So when DocumentSymbol has children, our client can't handle it correctly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* lsp: add workspace/symbol
* refactor symbol callback
* set hierarchical symbol support to true
* add documentation and default mapping
Co-authored-by: Hirokazu Hata <h.hata.ai.t@gmail.com>
|
|/ /
| |
| |
| | |
* support LocationLink in callbacks
* announce linkSupport in client capabilities
|
|/
|
|
|
|
| |
When attr_id is 0, the cursor's colors should be swapped, otherwise the
cursor might be invisible.
Closes #12198
|
| |
|
|\
| |
| | |
lsp/completion: Expose completion_item under completed_items.user_data + vim-patch:8.2.0084
|
| |
| |
| |
| |
| | |
By passing through completion_item it's now possible for snippet plugins
to add LSP snippet support.
|
| |
| |
| |
| |
| |
| | |
Problem: Complete item "user_data" can only be a string.
Solution: Accept any type of variable. (closes vim/vim#5412)
https://github.com/vim/vim/commit/0892832bb6c7e322fcae8560eaad5a8140ee4a06
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit creates 4 new highlight groups:
- LspDiagnosticsErrorSign
- LspDiagnosticsWarningSign
- LspDiagnosticsInformationSign
- LspDiagnosticsHintSign
These highlight groups are linked to their corresponding LspDiagnostics
highlight groups by default.
This lets users choose a different color for their sign columns and
virtualtext diagnostics.
|
| | |
|
|/
|
|
|
| |
ref: #12164
fix #12201
sign_getdefined() returns a list, {} if the sign is not defined.
|
| |
|
|
|
|
| |
CompleteChanged
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: The "last used" info of a buffer is under used.
Solution: Add "lastused" to getbufinfo(). List buffers sorted by last-used
field. (Andi Massimino, closes vim/vim#4722)
https://github.com/vim/vim/commit/52410575be50d5c40bbe6380159df48cfc382ceb
|
| |
| |
| |
| |
| |
| | |
Problem: Cannot filter :ls output for terminal buffers.
Solution: Add flags for terminal buffers. (Marcin Szamotulski, closes vim/vim#2751)
https://github.com/vim/vim/commit/0751f51a5b428805a8c1e9fe529693d032bec991
|
| |
| |
| | |
fix #12162
|
| |
| |
| | |
Messed this up in ef0398fe88e6cc74f33fb20519997774168d7832
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According to the spec there is the possibility that when a
VersionedTextDocumentIdentifier is used in a TextEdit the value may be
null. Currently we don't check for this and always assume that it's set.
So currently if a TextEdit comes in for a rename for example with the
version null, it fails as we are comparing the bufnumber with nil.
https://microsoft.github.io/language-server-protocol/specification#versionedTextDocumentIdentifier
|
| |
| |
| |
| |
| |
| | |
The method with the name 'textDocument/peekDefinition' is not part of
the official language server protocol specification. Therefore no
language server can/will support this. Thereby all related code and
documentation as been removed.
|