Treesitter update from #912 causing issues with org-roam #916
-
I don't know, if this is the right place to ask. When I update to an orgmode version past #912 (I git-bisected it) I get a strange error on startup. I reinstalled my Treesitter grammar with I didn't opened a bug report, because I'm not sure, if the problem is on my side. I am also not sure, if the problem is in org-roam, but then at least the breaking-changes information seems not entirely complete. @kristijanhusak Can you shed a bit more light on the implications of #912? @chipsenkbeil FYI. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
@seflue what does the |
Beta Was this translation helpful? Give feedback.
-
@kristijanhusak Thanks for this very fast answer.
|
Beta Was this translation helpful? Give feedback.
-
Are you using lazy? Do you get prompt to reinstall when running |
Beta Was this translation helpful? Give feedback.
-
I am using lazy. And yes, I get this prompt and I said "Yes, reinstall". |
Beta Was this translation helpful? Give feedback.
-
No it didn't . The timestamp of the org.so file actually matched the time, when I did the last reinstall before I manually deleted the file, so the reinstall seems to work, but it doesn't fix my issue. |
Beta Was this translation helpful? Give feedback.
-
I don't get the exception anymore, but I don't get any highlighting. When I have the org-bullets plugin enabled, I get the same error as soon as I open an org file. |
Beta Was this translation helpful? Give feedback.
I updated checkhealth on master to check for any conflicting parsers and report them. You can try that to see if there are some conflicts.