-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:help
docs look broken
#128
Comments
Don't think this is related to the grammar (this repo), unless #125 was already added to Nvim and caused a regression? @ObserverOfTime |
Can confirm @ObserverOfTime |
I use https://github.com/nvim-treesitter/nvim-treesitter and it is updated to commit 90a3962 there |
If the parser works then it's likely an issue with the tooling. I'll update Neovim to HEAD and check. |
I have tree-sitter 0.22.1 if that matters |
Yep, worked on neovim/neovim@6d680d9 (last commit I'd built) but is broken on neovim/neovim@8955cef. |
@AlexKurisu can you try the latest commit? |
Ackshually, some docs have multiple modelines. 🤓 |
Please bisect then. The last commit is unrelated. |
I don't know how :( |
Rather unsurprisingly, it's neovim/neovim@cb46f6e |
Yeah I figured that was one of the likely candidates. |
neovim/neovim#27853 is the upstream issue. (Note that the queries bundled in Neovim -- which differ from those here -- do not have this issue, so copying those to your config is a workaround in the meantime.) |
Nothing explains that commit, which is why I immediately reverted it. I would have force-pushed to erase it from existence if that were allowed. |
NVIM v0.10.0-dev-2590+g8955cef0c6.
![image](https://private-user-images.githubusercontent.com/60626727/312784236-062e9fa1-5bef-4170-9b27-f217296b9cae.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1NDAyNTksIm5iZiI6MTcyMDUzOTk1OSwicGF0aCI6Ii82MDYyNjcyNy8zMTI3ODQyMzYtMDYyZTlmYTEtNWJlZi00MTcwLTliMjctZjIxNzI5NmI5Y2FlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA5VDE1NDU1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdmZmJlNTI0MTUyMTdhYzk1ZmM1NzJmZjhhZTBjYzA1MmRlOGFmNGRmN2FlZWQ0NjhjYWNkNjkyMDQwYjNlZDImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.WjmXq4hU6FYV9DWTjC9J3AQB8atq04NgEaUmjVpBqws)
:help
docs look broken.:help vim.diagnostic.Opts
, for example, looks like this:This is not a colorscheme problem as nothing changes after switching to
:colorscheme default
The text was updated successfully, but these errors were encountered: