| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
| |
- remove incorrect usage of docstrings
- fix make_formatting_params return type documentation to 'DocumentFormattingParams'
- make progress_handler private
- fix links
|
| |
|
|
|
|
| |
the `textDocument/rangeFormatting` nad `textDocument/formatting` did not
pass bufnr to apply_text_edits, meaning edits were applied to
the user's currently active buffer. This could result in text being
applied to the wrong buffer.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ipairs terminates on the first nil index when iterating over table keys:
for i,k in ipairs( {[1] = 'test', [3] = 'test'} ) do
print(i, k)
end
prints:
1 test
Instead, use pairs which continues iterating over the entire table:
for i,k in pairs( {[1] = 'test', [3] = 'test'} ) do
print(i, k)
end
prints:
1 test
3 test
|
| |
|
|
|
|
|
|
|
|
| |
`return err_message(tostring(err))` caused errors to be printed as
`table: 0x123456789` instead of showing the error code and error
message.
This also removes some `if err` blocks that never got called because at
the end of `handlers.lua` all the handlers are wrapped with logic that
adds generic error handling.
|
| |
|
|
|
|
|
|
|
| |
results
Relates to https://github.com/neovim/neovim/issues/15050
Users should get some indication if there was an error or an empty
result.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Before:
Lens1Lens2
After:
Lens1 | Lens2
Fixes https://github.com/neovim/neovim/issues/15048
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds indentation that matches the number prefix to ensure diagnostic
messages spawning multiple lines align.
Before:
Diagnostics:
1. • Variable not in scope: red :: t0 -> t
• Perhaps you meant one of these:
‘rem’ (imported from Prelude), ‘read’ (imported from Prelude),
‘pred’ (imported from Prelude)
2. • Variable not in scope: repeDoubleColon :: [Char] -> t0
• Perhaps you meant ‘replaceDoubleColon’ (line 32)
After:
Diagnostics:
1. • Variable not in scope: red :: t0 -> t
• Perhaps you meant one of these:
‘rem’ (imported from Prelude), ‘read’ (imported from Prelude),
‘pred’ (imported from Prelude)
2. • Variable not in scope: repeDoubleColon :: [Char] -> t0
• Perhaps you meant ‘replaceDoubleColon’ (line 32)
|
| | |
|
| |
|
|
| |
(#15023)
|
| | |
|
| | |
|
| | |
|
| |
|
| |
No point in adding and then subtracting I believe ;)
|
| | |
|
| | |
|
| |\
| |
| | |
fix(lsp): Handle nil message_callbacks
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `onexit` handler could set `message_callbacks` to `nil` within the
luv event loop while the mainloop runs a function that tries to access
`message_callbacks`.
This adds some checks to prevent errors in that case.
Fixes https://github.com/neovim/neovim/issues/14863
|
| |\ \
| | |
| | | |
feat(lsp): use `g:markdown_fenced_languages` in `vim.lsp.util.stylized_markdown`
|
| | |/ |
|
| |/
|
|
|
| |
Given that the input is pre-filled with a path, it should be possible to
use dir completion.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Add the buffer number to the `textDocument/formatting` request, so
that it is passed to the handler.
The built-in formatting handlers do not use the buffer number, but user
overrides should have access to it.
|
| | |
|
| | |
|
| |
|
|
|
| |
`lsp.diagnostic.get_all()` was returning diagnotics for `:bwipeout`-ed
buffers because the diagnostic cache is not cleared. The first argument
of on_detach callback is the string "detach", not the bufnr.
|
| | |
|
| |\
| |
| | |
[RDY] fix(lsp): guard against negative diagnostic line numbers
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
fix(lsp): convert_input_to_markdown_lines: preserve plaintext
|
| | | |
|
| |/
|
|
| |
Closes #14743
|
| |
|
|
|
| |
Makes it easier to re-use the logic to populate the quickfix list
instead of the location list.
|
| |\
| |
| | |
fix(lsp): max 1 floating preview per buffer. Fixes #11508
|
| | | |
|
| | |
| |
| |
| | |
add option to show workspace diagnostic instead of the current buffer's
|
| | | |
|
| |\ \
| | |
| | | |
fix(lsp): set_loclist should target current win
|
| | |/
| |
| |
| |
| |
| | |
Currently, for large number of diagnostics, the delay in populating
loclist may be sufficient for a user to switch to another window,
resulting in the loclist being populated on the wrong window.
|
| |\ \
| | |
| | | |
fix(lsp): floating window border size for string type
|
| | |/ |
|
| |/
|
|
|
|
| |
Adding the line takes up valuable horizontal screen space, and also
precludes using the quickfixtextfunc built into neovim due to the
harcoded `|`.
|
| |\
| |
| |
| |
| | |
shadmansaleh/enhance/lsp/make_focusable_parameter_configurable
feat(lsp): Make focusability of lsp float configurable
|
| | |
| |
| |
| |
| |
| | |
In the documentation for `vim.lsp.util.open_floating_preview`
the opts table keys were prefixed with `--` instead of `---`,
preventing capture by docgen.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This pr allows the user to specify whether `lsp.utils.open_floating_preview`
is focusable via the `opts` parameter. Defaults to true.
It can be configured by setting the focusable key inside opts parameter:
```lua
vim.lsp.util.open_floating_preview(contents, syntax, {focusable = false})
```
|
