| Commit message (Collapse) | Author | Age |
... | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Problem: The eval.txt help file is too big.
Solution: Split off testing support to testing.txt. Move function details
to where the functionality is explained.
https://github.com/vim/vim/commit/ed997adaa1e9bd057ce732a73d933b739e9d0c30
Vim commit 5477506a9f01d40fad2e8f0555bc37adee30478f
contains the duplicate tag fix in runtime/doc/testing.txt.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
template: make sure people read `:h vim-differences`
|
| | |_|_|/ /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
get_str_line: Replace grow_array usage
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A single xmemdupz is sufficient, as it is already
zero-terminating the string
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
[RDY] tree-sitter ensure there is a nested table allocated for `#set!`
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes the following bug:
```
test/functional/helpers.lua:107: Error executing lua:
vim/treesitter/query.lua:256: attempt to index a nil value
```
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
lsp: deep copy vim.lsp.log when reloading
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
If vim.lsp.log is loaded the second time,
the vim.log.levels will be modified with additional
entries from 0-5.
This will cause the require to fail as level:lower does
not exists on numbered value.
|
|\ \ \ \ \ \ \
| |_|_|_|_|/ /
|/| | | | | | |
[RDY] Fix get str line
|
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The stack allocated buffer does introduce an arbitrary limit,
to the length of the line.
Previously, if the line was too long, it might be catched by a
stack smash canary or resulted into a crash.
This is not guaranteed though, and thus could result into undefined
behavior.
To mitigate this, an dynamic allocated buffer is replacing the stack
allocated buffer, with the initial capacity of the copied line.
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
[LSP] Support for sequential formatting with multiple clients
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
On Windows, `new_lnum + MAXLNUM` causes overflow and as a result the
line number of that sign becomes invalid negative number. This occurs
when the `set signcolumn=yes`, in other words `signcolumn` is not `auto`
and the sign column is less than 2 columns.
The related change was made in the commit
f2ed7605da45eb79a4f7bb89fb19f680fb5a4927. Originally the above addition
is only executed if `amount != MAXLNUM`, so reintroducing this check
fixes the bug and will hardly produces a new bug.
Fixes https://github.com/neovim/neovim/issues/14460
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This fixes a regression that was introduced in [1] by accidentally leaving out a line.
1: https://github.com/neovim/neovim/pull/12262
|
| | | | | |
| | | | | |
| | | | | | |
Closes https://github.com/neovim/neovim/issues/14467
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* doc & fixes: Generate treesitter docs
* fixup to treesitter-core
* docs(treesitter): fix docs for most functions
Co-authored-by: Thomas Vigouroux <tomvig38@gmail.com>
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
decorations: right_align and win_col
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
lsp: Allow decoded.result to be `false`
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some servers might respond to `workspace/executeCommand` requests with a
boolean result and that could be `false`.
A `false` result should be allowed and not trigger the `on_error`
handler:
-- Invalid server message
on_error(client_errors.INVALID_SERVER_MESSAGE, decoded)
Concrete example where this occurred is with eclipse.jdt.ls:
vim.lsp.buf_request(
0,
'workspace/executeCommand',
{
command = 'java.project.isTestFile',
arguments = { vim.uri_from_bufnr(0), },
},
function(err, _, resp)
print(vim.inspect(err), vim.inspect(resp))
end
)
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
[WIP] startup: do "syntax enable" instead of "syntax on" after init.vim
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
"syntax on" overwrites existing highlight groups, while "syntax enable"
just sets missing groups. This change prevents user defined highlights in
init.vim/lua to get overwritten. The manual recommends "syntax enable" for
new configurations anyway, "on" command was probably used as it is the
implicit default.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
fix(pvscheck): Switch URL to pvs-studio.com
|
|/ / / /
| | | |
| | | |
| | | | |
[skip ci]
|
|\ \ \ \
| | | | |
| | | | | |
Update permissions for vim-patches workflow
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Avoids hard-coding branch names.
[skip ci]
|
| | | | |
| | | | |
| | | | |
| | | | | |
[skip ci]
|
|/ / / /
| | | |
| | | |
| | | | |
[skip ci]
|
|\ \ \ \
| |_|_|/
|/| | | |
ui_compositior: handle overlapping displayed floats in the same tick
|
|/ / /
| | |
| | |
| | |
| | | |
problem: the order of non-focuesed float opened before focused float is wrong (sunjon)
solution: check curwin and correct the order (bfredl)
|
|\ \ \
| | | |
| | | | |
doc : fixing missing @return in nvim_open_term doc
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
[LSP] - Don't automatically force shutdown on second restart.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is maybe a bit of a niche case, but I hit on this often as I'm
developing a server, and therefore continually restarting it to get the
latest changes of the server. Previously, I could only do this once
since if you send in a request to restart/shut down the server, it will
register it as a `tried_graceful_shutdown = true` meaning that the next
restart would force it to be killed instead of another graceful exit.
Instead, this changes the name a bit and now it will only mark
`graceful_shutdown_failed = true` _if_ it actually fails to gracefully
shutdown. This change allows for a user to restart multiple times in a
situation like mine where nothing is going wrong, but I just want to
restart continually as I'm developing without having to close and
reopen.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit prevents two things regarding the tagstack and jumping to
locations:
- Pushing the same item twice in a row
- Pushing an item where the destination is the same as the source
Both prevent having to press CTRL-T additional times just to pop items
that don't make the cursor move.
|
|\ \ \ \
| | | | |
| | | | | |
Revert "lsp: fix blocking in closing of clients"
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 2e6c09838f88803f31d229002715628639631897.
* Fixes #14428
* This commit caused neovim to close while open handles to the uv timer
to kill active language servers were still open
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allow to sort diagnostics (and thus signs and virtual text) by severity, so that
the most important message is shown first.
vim.lsp.handlers['textDocument/publishDiagnostics'] = vim.lsp.with(
vim.lsp.diagnostic.on_publish_diagnostics, {
severity_sort = true,
}
)
Fixes https://github.com/neovim/neovim/issues/13929
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'splitright' (#14398)
Problem: :mksession uses current value of 'splitbelow' and 'splitright'
even though "options" is not in 'sessionoptions'. (Maxim Kim)
Solution: Save and restore the values, instead of setting to the current
value. (closes vim/vim#8119)
https://github.com/vim/vim/commit/0995c81f2ffe276669daa004f7778ecc6f5ee09d
Patch v8.2.1682 is not ported.
Replace "goto fail;" with "return FAIL;".
|
| | |
| | |
| | |
| | |
| | | |
Previously vim.cmd was an alias of nvim_command().
From now on it is an alias of nvim_exec().
|