| Commit message (Collapse) | Author | Age |
... | |
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Some jsonc files are not recognized.
Solution: Add patterns for jsonc and move some from json to jsonc.
(closes vim/vim#11711)
https://github.com/vim/vim/commit/104b2ff4d0ec9248ba0b979aa3bbccb65fcad422
Co-authored-by: kylo252 <59826753+kylo252@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: MS-Windows: most users expect using Unicode.
Solution: Default 'encoding' to utf-8 on MS-Windows. (Ken Takata,
closes vim/vim#3907)
https://github.com/vim/vim/commit/f883d9027c750967b115b82de984ee449ab17aa8
Correct the encoding of the file.
Co-authored-by: K.Takata <kentkt@csc.jp>
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | | |
vim-patch:9.0.{1078,1079}
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Leaking memory when defining a user command fails.
Solution: Free "compl_arg" when needed. (closes vim/vim#11726)
https://github.com/vim/vim/commit/33e543038b84af7557ab9ecff500fc4ab98dd2a3
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: With the +vartabs feature indent folding may use wrong 'tabstop'.
Solution: Use the "buf" argument instead of "curbuf".
https://github.com/vim/vim/commit/07146ad1d33ba0d36b324873e5c461931e6b025e
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem:
See #20628. Terminals supporting cursor color changing usually set the
"user-defined" `Cs` terminfo capability. Most terminals expect the parameter to
the capability to be a string (in hex format like `#0099ff` or like
`rgb:00/99/ff`), others may expect a number.
Nvim currently can't handle string parameters, causing terminals to receive
a bogus command.
Unfortunately, as the `Cs` capability is "user-defined", there's no strict
format. The parameter it takes isn't really standardized. It seems most
terminals in use follow xterm; iTerm appears to be an exception.
Solution:
Use the `Cs` capability more reliable by following terminfo and
sending the color in hex format, at the cost of using unibilium string vars.
Alternatively, could revert https://github.com/neovim/neovim/commit/34d41baf8a8e4ab8c006b7f29a8106e60e311aa2
and hardcode the specific format required by terminals, instead of reading
terminfo.
Fixes #20628
Fixes #19607
|
| | |
| | |
| | | |
Sort diagnostics by column number in quickfix list
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: screenpos() column result in fold may be too small.
Solution: Add space of 'number', sign column, etc. (closes vim/vim#11715)
https://github.com/vim/vim/commit/ba2d19193201277397c25c1f5a134ea042542555
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The BufWipeout autocmd is not 100% reliable and may leave stale entries
in the cache. This is sort of a hack/workaround to ensure
`vim.diagnostic.reset` calls don't fail if there are stale cache entries
but instead clears them
Fixes errors like
Error executing vim.schedule lua callback: /usr/share/nvim/runtime/lua/vim/diagnostic.lua:1458: Invalid buffer id: 22
stack traceback:
[C]: in function 'nvim_exec_autocmds'
/usr/share/nvim/runtime/lua/vim/diagnostic.lua:1458: in function 'reset'
|
| |\ \
| | | |
| | | |
| | | | |
feat(lsp): add function to get semantic tokens at cursor
feat: `vim.inspect_pos()`, `vim.show_pos()` and `:Inspect[!]`
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
vim-patch:8.2.{1208,1209,1210}: using ht_used when looping through a hashtab is less reliable
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
reliable
Problem: Using ht_used when looping through a hashtab is less reliable.
Solution: Use ht_changed in a few more places.
https://github.com/vim/vim/commit/1f22cc5cdb2da867d6bbf54dd371f279c38a2f56
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem: Vim9: test failure.
Solution: Add missing changes to hashtab.
https://github.com/vim/vim/commit/21c16f868d725fffc8fa36620cba33dd5f2ed576
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Build failure.
Solution: Add missing change.
https://github.com/vim/vim/commit/49fe0d6b289ee640cf5c49b1704bbbd641a0237d
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| | | |
| | | |
| | | | |
Also remove some duplicate unsigned long casts.
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
refactor(params): open -s and -w script files after parsing commands
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will be needed for #18375 as only the server should open the.
scriptfile, and redirected stdin fd will need to be used.
Also executing actions in the middle of command_line_scan() is cringe.
|
| |/ / /
| | | |
| | | | |
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
doing (#21429)
Problem: Some test function names do not match what they are doing.
Solution: Leave out user data for the test that is called "NoUserData".
(closes vim/vim#11703)
https://github.com/vim/vim/commit/4cd45f1408321905019614b40a2173fe0456a96d
Nvim's tests already match function names. Add missing indent changes
and a missing comment from patch 8.2.0084.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Using team reviewers when possible reduces the churn on the git history
as we'll be able to add or remove reviewers without needing to change
the workflow files.
This requires using Github fine-grained personal access tokens with Pull
Requests set to "Read and write" and Members to "Read-only".
|
| |\ \ \
| | | | |
| | | | | |
fix(lua): always return nil values in vim.tbl_get when no results
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While `return` and `return nil` are for most intents and purposes
identical, there are situations where they're not. For example,
calculating the amount of values via the `select()` function will yield
varying results:
```lua
local function nothing() return end
local function null() return nil end
select('#', nothing()) -- 0
select('#', null()) -- 1
```
`vim.tbl_get` currently returns both nil and no results, which makes it
unreliable to use in certain situations without manually accounting for
these discrepancies.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
fix(treesitter): check buffer is loaded when restoring options
Also restore spelloptions
Fixes #21416
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
detection (#21417)
Problem: Conflict between supercollider and scala filetype detection.
Solution: Do not check for "Class : Method", it can appear in both
filetypes. (Chris Kipp, closes vim/vim#11699)
https://github.com/vim/vim/commit/70ef3f546b6ef83e463e91b7e388d9c68ad58894
Co-authored-by: Chris Kipp <ckipp@pm.me>
|
| | | | |
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: After a failed CTRL-W ] next command splits window.
Solution: Reset postponed_split. (Rob Pilling, closes vim/vim#11698)
https://github.com/vim/vim/commit/cb94c910706fdd575cc25797d7858e084f1e3524
Co-authored-by: Rob Pilling <robpilling@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Using freed memory when autocmd changes mark.
Solution: Copy the mark before editing another buffer.
https://github.com/vim/vim/commit/8ecfa2c56b4992c7f067b92488aa9acea5a454ad
Nvim already copies the mark.
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| |/ |
|
| |\
| | |
| | | |
fix(tests): initialize Screen.colors in API highlight tests
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Apply semantic token modifiers as separate extmarks with corresponding
highlight groups (e.g., `@readonly`). This is a low-effort PR to enable
the most common use cases (applying, e.g., italics or backgrounds on top
of type highlights; language-specific fallbacks like `@global.lua` are
also available). This can be replaced by more complicated selector-style
themes later on.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of testing for every possible modifier type, only test bits up
to the highest set in the token array. Saves many bit ops and
comparisons when there are no modifiers or when the highest set bit is a
lower bit than the highest possible in the legend on average.
Can be further simplified when non-luaJIT gets the full bit module (see #21222)
|
| | |
| | |
| | | |
Fixes https://github.com/neovim/neovim/issues/21388
|
| | |
| | |
| | | |
Co-authored-by: ii14 <ii14@users.noreply.github.com>
|
| | |
| | |
| | | |
Closes https://github.com/neovim/neovim/issues/18225
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* vim-patch:7db29e4b5c3a
Update runtime files
https://github.com/vim/vim/commit/7db29e4b5c3a347d24ca5062ddaa5cf4c4d54b9c
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| | |
| | |
| | |
| | |
| | |
| | | |
- https://github.com/neovim/tree-sitter-vimdoc v1.2.4 eliminates most
errors in pi_netrw.txt, so we can remove that workaround from
ignore_parse_error().
- improved codeblock
|
| | | |
|