| Commit message (Collapse) | Author | Age |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Matchparen is slow.
Solution: Actually use the position where the match started, not the
position where the search started. (closes vim/vim#11644)
https://github.com/vim/vim/commit/79336e19cb39322d45a787c33b83cce3b314a012
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
|/
|
|
|
|
|
|
|
|
|
| |
Problem: CmdlineChange event triggered twice for CTRL-R.
Solution: Return CMDLINE_NOT_CHANGED from cmdline_insert_reg().
(closes vim/vim#8219)
https://github.com/vim/vim/commit/796139ae3ac89e27ee96dce3c7fdb87d8c839f53
Cherry-pick Test_cmdline_map_cmdlineChanged() from patch 8.2.2851.
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
|
|
| |
This is the same code change as https://github.com/vim/vim/commit/6c87bbb4e45515e70ac1728cabd1451063bf427d
|
|
|
|
|
|
|
|
| |
The spec indicates that the response may be `null`, but it doesn't
really say what a `null` response means. Since neovim raises an error if
the response is `null`, I figured that ignoring it would be the safest
bet.
Co-authored-by: Mathias Fussenegger <f.mathias@zignar.net>
|
|\
| |
| | |
fix(vim-patches): ensure libfuse is installed
|
| | |
|
| |
| |
| |
| |
| | |
Unlike split windows, creating a new floating window does not cause
other windows to resize, so it doesn't make much sense to trigger
WinScrolled or WinResized when creating a new floating window.
|
| |
| |
| | |
Follow up to https://github.com/neovim/neovim/pull/21337
|
|/ |
|
|
|
|
|
|
| |
Problem: Function name does not match what it is used for.
Solution: Include the modifier in the name. (closes vim/vim#11679)
https://github.com/vim/vim/commit/ffa4e9b43a3d6d7f412f54637a4b1076ed2bc2f4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. The algorithm for applying edits was slightly incorrect. It needs to
preserve the original token list as the edits are applied instead of
mutating it as it iterates. From the spec:
Semantic token edits behave conceptually like text edits on
documents: if an edit description consists of n edits all n edits are
based on the same state Sm of the number array. They will move the
number array from state Sm to Sm+1.
2. Schedule the semantic token engine start() call in the
client._on_attach() function so that users who schedule_wrap() their
config.on_attach() functions (like nvim-lspconfig does) can still
disable semantic tokens by deleting the semanticTokensProvider from
their server capabilities.
|
|
|
|
|
|
|
|
|
|
|
|
| |
off (#21355)
Problem: Shift-Tab shows matches on cmdline when 'wildmenu' is off.
Solution: Only show matches when 'wildmode' contains "list". (closes vim/vim#10951)
https://github.com/vim/vim/commit/300175fd7f874be78826a00f5cb60a7ec2f20655
Code change has already been ported.
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(#21352)
Problem: Command line completion doesn't always work properly.
Solution: Adjust triggering after a "|". Add more tests. (Yegappan
Lakshmanan, closes vim/vim#9779)
https://github.com/vim/vim/commit/e3846cf1ebdc4af0b39885153b4703f71a9b919e
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
|
|\
| |
| | |
vim-patch:8.2.{4366,4376}: cmdline completion tests
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Not enough tests for command line completion.
Solution: Add a few more tests. (Yegappan Lakshmanan, closes vim/vim#9771)
https://github.com/vim/vim/commit/9773db6f9bce7a6f063e23179976d7825ace4d72
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
|
|/
|
|
|
|
|
|
|
| |
Problem: Not enough tests for command line completion.
Solution: Add a few more tests. (Yegappan Lakshmanan, closes vim/vim#9760)
https://github.com/vim/vim/commit/4d03d870007c593bce2cfa8d0a6597ca3a20fa35
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
|
|
|
|
| |
I've noticed a patch 8.2.4376 that uses more Xtest directories.
Change $TMPDIR to X-test-tmpdir to avoid more future divergence.
|
|\
| |
| | |
vim-patch:9.0.1036: undo misbehaves when writing from an insert mode mapping
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Problem: Undo misbehaves when writing from an insert mode mapping.
Solution: Sync undo when writing. (closes vim/vim#11674)
https://github.com/vim/vim/commit/3f8f82772313af9f2417b06651f30988b63e1c96
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| |
|
|
|
|
|
|
|
| |
Problem: `chansend()` on Windows sends lines in reverse order.
Cause: Using \n instead of \r\n for newlines on Windows.
Solution: on Windows, use CRLF newline characters.
Fixes #18501
|
|\
| |
| | |
vim-patch:9.0.{1030,1032}: using freed memory with the cmdline popup menu
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Test fails when terminal feature is missing.
Solution: Use CheckRunVimInTerminal.
https://github.com/vim/vim/commit/b9603f6498e5637e111bd1dca0eab88c8dd0f99b
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
|/
|
|
|
|
|
|
|
| |
Problem: Using freed memory with the cmdline popup menu.
Solution: Clear the popup menu when clearing the matches. (closes vim/vim#11677)
https://github.com/vim/vim/commit/038e6d20e680ce8c850d07f6b035c4e1904c1201
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|