-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
vimPlugins.nvim-treesitter: workaround for duplicate grammars #339589
Conversation
See also #319233 (comment) Result of 1 package built:
|
Im completely fine with this solution for this purpose for the reasons stated in my most recent comment on the other thread |
I forgot to mention, yes, I did rebuild agaisnt the branch It also still works with the norg overlay active and all the other random stuff I could throw at it like multiple ones on different versions. |
Not sure what to do with the other PR but let's get this in as this seems to restore the previous behavior. |
I will work on it, but later |
I started getting this error messages when starting neovim after the last update:
Could this be related? |
doesnt look like it. Looks more like one of the two things pointed out in this thread: Try not lazy loading treesitter and/or making sure your parsers are in the RTP BEFORE the builtin |
The issue fixed by this PR was a build time issue, and it just removes duplicates rather than failing the build on duplicates. I would be very surprised if this error came from this PR. Your error looks like an issue with load order at startup, something this PR didn't change. |
Thanks for clarifying. it was indeed an error with leftover files in ~/.config/share. Solved! |
Description of changes
See #339076 (comment)
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)@BirdeeHub, could you please try rebuilding your system on this PR and see if the issue persists? I didn't test this.
Add a 👍 reaction to pull requests you find important.