-
-
Notifications
You must be signed in to change notification settings - Fork 42
Add r treesitter #97
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
Add r treesitter #97
Conversation
I think I'm blocked adding r support to cursorless until this is merged, because I can't get it to build locally |
out unfortunately I think the answer is #93 (comment). I don't have capacity to work on at this moment but if you want to take a crack I can help you get up to speed. |
Ok we've moved all the wasm stuff into https://github.com/cursorless-dev/tree-sitter-wasms so you can move the package.json dependency piece there and then we'll release a new version of that package. That way you don't need to worry about building wasms; it happens in CI |
Waiting on cursorless-dev/tree-sitter-wasms#17 which in turn is waiting on a npm package. |
@AndreasArvidsson does this repo AND cursorless need to be updated for the new wasms to appear? Is there a way to use a local build of parse tree with cursorless? |
Yes. This repository uses the wasm and Cursorless uses this extension. vscode-parse-tree/package.json Line 85 in 260356d
But normally you would just use the |
Published |
|
Oh sorry Andreas, it looks like at some point I overwrote my changes to the package json and it did not update the wasms dependency |
Oh my bad. I should have double check that. Do you mind creating a new pull request on this repository with dependency |
oh, I thought I had, but it isn't there. Must have forgot to confirm it. Done now |
Sadly I was unable to get this to actually build, across two different distros. I presume this is to do with the current "cursed state" of the repo? Is this an issue for merging?
I seem to have an old version of treesitter, 0.22.6, related to this issue #93 (comment)
the error I get is the same: