rneovim.git/runtime/lua, branch fix_semantic_tokens_pull Neovim fork with Rahm's personal hacks. fix(semantic_tokens.lua): Fix nil tokens/data in semantic_tokens.lua 2023-01-19T20:42:40+00:00 Josh Rahm rahm@google.com 2023-01-19T19:37:12+00:00 409e6f9d7e690a398c4318a8eab7fd56a2eceda3 Some (poorly-implemented) LSPs can return an empty JSON object in LSP responses, which could cause tokens to be nil, which would eventually cause an error and a bad UI experience. This fix makes sure that the tokens variable is always set to a non-nil value. 
Some (poorly-implemented) LSPs can return an empty JSON object in
LSP responses, which could cause tokens to be nil, which would eventually
cause an error and a bad UI experience. This fix makes sure that the
tokens variable is always set to a non-nil value.
fix(treesitter): really restore syntax 2023-01-17T16:56:23+00:00 Lewis Russell lewis6991@gmail.com 2023-01-17T16:56:23+00:00 20b7be2d1024b6e9eac68e0cb92cf663e95e51ca - also unset b:ts_highlight on stop() Fixes: #21836 
- also unset b:ts_highlight on stop()

Fixes: #21836
 feat(health): detect tmux RGB support via `client_termfeatures` 2023-01-16T15:30:57+00:00 Sean Dewar seandewar@users.noreply.github.com 2023-01-16T13:25:11+00:00 7e24c45221b330ccf8ed3808570dab38d212ba2e Problem: On tmux v3.2+, the `terminal-features` option may be used to enable RGB capabilities over `terminal-overrides`. However, `show-messages` cannot be used to detect if RGB capabilities are enabled using `terminal-features`. Solution: Try to use `display-message -p #{client_termfeatures}` instead. The returned features include "RGB" if either "RGB" is set in `terminal-features`, or if "Tc" or "RGB" is set in `terminal-overrides` (as before). Nothing is returned by tmux versions older than v3.2, so fallback to checking `show-messages` in that case. Also, un-Vimscriptify the previous logic a bit, and change the error message to point to using the `terminal-features` option instead for newer tmux versions. 
Problem: On tmux v3.2+, the `terminal-features` option may be used to enable RGB
capabilities over `terminal-overrides`. However, `show-messages` cannot be used
to detect if RGB capabilities are enabled using `terminal-features`.

Solution: Try to use `display-message -p #{client_termfeatures}` instead.
The returned features include "RGB" if either "RGB" is set in
`terminal-features`, or if "Tc" or "RGB" is set in `terminal-overrides` (as
before).
Nothing is returned by tmux versions older than v3.2, so fallback to checking
`show-messages` in that case.

Also, un-Vimscriptify the previous logic a bit, and change the error message to
point to using the `terminal-features` option instead for newer tmux versions.
fix(health): fix `tmux_esc_time` comparison 2023-01-16T14:26:29+00:00 Sean Dewar seandewar@users.noreply.github.com 2023-01-16T10:37:14+00:00 60df0c06510cc65d68a2693722577d437264f67d Regression from the health.vim to .lua changes. Unlike Vim script, Lua does not implicitly convert strings to numbers, so this comparison threw an error. 
Regression from the health.vim to .lua changes.

Unlike Vim script, Lua does not implicitly convert strings to numbers, so this
comparison threw an error.
docs: treesitter.add_directive, add_predicate #21206 2023-01-16T12:39:19+00:00 Ching Pei Yang 59727193+horriblename@users.noreply.github.com 2023-01-16T12:39:19+00:00 ef89f9fd46ab591183b7f59f31f5a2e55f7a526b 






health: migrate to Lua #21661
2023-01-16T09:55:24+00:00

TJ DeVries
devries.timothyj@gmail.com

2023-01-16T09:55:24+00:00

307efe4906de9f0b7d8611ea36bddb85493c1447

* refactor: remove all vimscript from nvim/health
* fixup: previous method broke if you had a folder named 'x-lua'




* refactor: remove all vimscript from nvim/health
* fixup: previous method broke if you had a folder named 'x-lua'






docs(lua): use luaref tag instead of www.lua.org #21813
2023-01-15T21:32:23+00:00

Naru
naru@naruaway.com

2023-01-15T21:32:23+00:00

34b973b1d9e3b0c6f546e3aa661c29edd5a1ab87












refactor: format with stylua (#21821)
2023-01-15T15:00:23+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2023-01-15T15:00:23+00:00

c752c853630898f38bcf46a9a5e9d83e41989eeb












vim-patch:9.0.1191: some Bazel files are not recognized (#21784)
2023-01-13T16:27:35+00:00

Christian Clason
c.clason@uni-graz.at

2023-01-13T16:27:35+00:00

fd3d30a22c2bcc7acd266214b761b44219aefbe7

Problem:    Some Bazel files are not recognized.
Solution:   Add an extra Bazel pattern. (Keith Smily, closes vim/vim#11807)

https://github.com/vim/vim/commit/3213952966896ffb1d8fa186bcf8c43359fca0f0

Co-authored-by: Keith Smiley <keithbsmiley@gmail.com>




Problem:    Some Bazel files are not recognized.
Solution:   Add an extra Bazel pattern. (Keith Smily, closes vim/vim#11807)

https://github.com/vim/vim/commit/3213952966896ffb1d8fa186bcf8c43359fca0f0

Co-authored-by: Keith Smiley <keithbsmiley@gmail.com>






feat(diagnostic): vim.diagnostic.is_disabled() #21527
2023-01-12T16:57:39+00:00

Raphael
glephunter@gmail.com

2023-01-12T16:57:39+00:00

572cd8031dd7c91ac9e17cbdfab16d87f1fed6b7