-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Not yet using tree-sitter.json
#64
Comments
At some point it looks like the Gave it a try here [1] and observed that some of the values that got into {
"grammars": [
{
"name": "clojure",
"camelcase": "Clojure",
"scope": "source.clojure",
"path": ".",
"file-types": [
"bb",
"clj",
"cljc",
"cljs"
]
}
],
"metadata": {
"version": "0.0.13",
"license": "MIT",
"description": "Clojure grammar for tree-sitter",
"links": {
"repository": "https://github.com/tree-sitter/tree-sitter-clojure"
}
},
"bindings": {
"c": true,
"go": true,
"node": true,
"python": true,
"rust": true,
"swift": true
}
} It may be that pre-emptively creating a Below is a draft of a possible {
"grammars": [
{
"name": "clojure",
"camelcase": "Clojure",
"scope": "source.clojure",
"path": ".",
"file-types": [
"bb",
"clj",
"cljc",
"cljs"
]
}
],
"metadata": {
"version": "0.0.13",
"description": "Clojure grammar for tree-sitter"
}
} Unfortunately, it looks like version info is now duplicated across two files. We may be stuck with this unless / until Cursorless stops needing On a side note, having both [1] Tested with:
though it's possible an earlier version exhibits similar behavior. |
The situation of grammars missing
|
I think at some point we should start using
tree-sitter.json
. The file is described here.Also, there is some more info about eventual removal of the
tree-sitter
section frompackage.json
here.I'd like to get rid of
package.json
, but I think Cursorless may still depend on it, so that may not happen so soon.(On a side note, the
build-wasm
command may be going away in 0.24; with recent releases you can already usebuild --wasm
the replacement. My attempts at getting the older subcommand to stay around longer did not meet with success. Backward compatibility of the cli API does not rank that highly priority-wise AFAIU.)The text was updated successfully, but these errors were encountered: