-
Notifications
You must be signed in to change notification settings - Fork 101
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
bug: Treesitter error with nvim-cmp
docs
#962
Comments
nvim-cmp
docsnvim-cmp
docs
If you comment out the line |
I think I know what's causing this. There's an upstream recent change where get_parser no longer errors when no parser is available and returns nil instead. Will look into it tomorrow. not home right now |
No problem. Thanks a lot 😄 |
Caused by neovim/neovim#30379 |
Should be fixed now. Let me know if the problem would persist |
🤖 I have created a release *beep* *boop* --- ## [4.5.2](v4.5.1...v4.5.2) (2024-10-02) ### Bug Fixes * **treesitter:** upstream API changes. Fixes [#962](#962) ([5070aae](5070aae)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
All good now. If I find something else over the next couple of days I'll comment here. Tnx again 😃 |
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.11.0-dev-881+g865ba42e0
Operating system/version
Linux Mint 21.3
Describe the bug
When auto-completing in Python files and the
nvim-cmp
completion menu pops up, when traversing through the available entries the following error pops upI don't see this error in Lua files and since I don't do anything else except Python and Lua, I'm not sure if this also occurs with other languages as well.
Steps To Reproduce
I'm using LazyVim distro but was also able to reproduce this without LazyVim with this minimal repro.
print
and go through the available entriesExpected Behavior
No error should pop up. I'm guessing this has something to do with the latest Treesitter changes on Neovim nightly, because it's not reproducible with Neovim stable 0.10.1.
Repro
The text was updated successfully, but these errors were encountered: