| Commit message (Collapse) | Author | Age |
|\
| |
| | |
deps(treesitter): bump C parser and runtime
|
|/
|
|
|
| |
It's been a while since we bumped the C parser version, and a few ABI
versions have been realised since.
|
|\
| |
| | |
vim-patch:8.2.{2392,2399,2402}
|
| |
| |
| |
| |
| |
| | |
Problem: Some filetypes not detected.
Solution: Detect Ruby Signature and Puppet related files. (Doug Kearns)
https://github.com/vim/vim/commit/8323cab31c3120a7f80cf3271a506a30ec04d99e
|
| |
| |
| |
| |
| |
| | |
Problem: Fold test fails in wide terminal.
Solution: Adjust the test. (Dominique Pelle, closes vim/vim#7731, closes vim/vim#7739)
https://github.com/vim/vim/commit/7cf0c114d690c91ac88c92a1a6f1b1935cb6410f
|
| |
| |
| |
| |
| |
| | |
Problem: Fennel filetype not recognized.
Solution: Detect with pattern and hashbang. (Chinmay Dalal, closes vim/vim#7729)
https://github.com/vim/vim/commit/402115f1c2b4d0704a822206f2e6e931e721c129
|
|/
|
| |
We should be consistent in sending the EOL character to servers(I think). Julia expects this to match on bufwrite, or it crashes when vim appends the newline during the write process.
|
|\
| |
| | |
Auto sign column with minimum size support
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Doc: Generate API docs for buf_set_extmark gravity
|
|/ /
| |
| |
| | |
Cf. #13679
|
| | |
|
|\ \
| | |
| | | |
vim-patch:8.2.{2375,2379,2384,2385}
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: "gj" and "gk" do not work correctly when inside a fold.
Solution: Move check for folding. (closes vim/vim#7724, closes vim/vim#4095)
https://github.com/vim/vim/commit/e71996bd0865659bde5450f466bc3e53e83431b2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Test for RGB color skipped in the terminal.
Solution: Run the GUI if possible.
https://github.com/vim/vim/commit/09fbedc8dc3adc0a7adf2093916911e633cfa626
Cherry-pick Test_highlight_RGB_color() from patch v8.2.1077
to port this patch.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Turtle filetype not recognized.
Solution: Add a rule to detect turtle files. (closes vim/vim#7722)
https://github.com/vim/vim/commit/5e6a7aa2b26077775906eb8411952dc6259694de
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Finding spell suggestions twice if 'spellsuggest' contains number.
Solution: Only do internal suggestions once. (closes vim/vim#7713)
https://github.com/vim/vim/commit/77a849c4b3d73c228013a047913c90834a93b4f6
|
|\ \ \
| | | |
| | | | |
Missing argument for package.loadlib()
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Allow for foo.bar.baz module name
Make luaopen_module() name compatible with Lua 5.1
|
|\ \ \
| | | |
| | | | |
api(echo): should clear cmdline before echo
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Extmarks api: allow for gravity
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
position of extmark
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| |_|/
|/| | |
api: nvim_echo
|
|/ / |
|
|\ \
| | |
| | | |
fix(languagetree): use tree nodes instead of regions in contains
|
|/ / |
|
|\ \
| | |
| | | |
treesitter: default start and end row when omitted
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
logic
This function returns the start and stop value if set else the node's range is used
When the node's range is used, the stop is incremented by 1 to make the search inclusive
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add support for default start and end row when omitted in the
query:iter_captures and query:iter_matches functions.
When the start and end row values are omitted, the values of the given
node is used. The end row value is incremented by 1 to include the node end
row in the match.
Updated tests and docs accordingly.
|
| | | |
|
| | |
| | |
| | |
| | | |
* update lua documentation
* run docgen
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `workspace/configuration` handler could fail with the following
error if `config.settings` is nil:
runtime/lua/vim/lsp/util.lua:1432: attempt to index local 'settings' (a nil value)"
This ensures that `config.settings` is always initialized to an empty
table.
|
|\ \ \
| | | |
| | | | |
Remove -Z flag from --help message
|
| | | | |
|
| |/ / |
|
| | |
| | |
| | | |
Set release date based on commit ee77d8665ffe327a2158354021bbbcb772b3521a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Add in clienInfo to initalize_params.
Some servers (like Metals in my case) will actually pull this
info from the initalize_params and display it in the logs. I
know from the server perspective it helps at times to have this
available to pull from to have more details about the client and
version. You can see that this is part of the spec here:
microsoft.github.io/language-server-protocol/specification#initialize
|
| | |
| | |
| | | |
Until we support dynamicRegistration, we should handle the client/registerCapability in core. There are still some language servers that send this request despite dynamicRegistration not being registered client-side (we got an upstream fix for the node ones, but this depends on them bumping vscode-languageserver-node).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The page is useful because it contains:
How to install it
Package information (e.g. current version)
List of dependencies
Analytics (how many people are using it)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
retrun a structured version dict
:lua print(vim.inspect(vim.version()))
{
api_compatible = 0,
api_level = 7,
api_prerelease = true,
major = 0,
minor = 5,
patch = 0
}
|