You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tree-sitter grammars are currently all added to the project as git submodules. There are quite a few supported languages now, so it ends up being very expensive to clone helix.
It may make sense to have a separate CLI to do fetching and grammar compilation in the future, but for now it looks like a nice and small increment to switch submodules out for a script like this one in tree-sitter itself. A shallow clone for each grammar would be faster.
There are also some packaging methods that have a hard time with submodules which a script may improve. See void-packages#33881 and #1448.
The text was updated successfully, but these errors were encountered:
To add to this, I've been having an issue recently where the submodules say they're updated, but don't actually clone any of the data. This causes the build script in helix-syntax to fail. But it's frustrating when it's only a few of the grammars, so you're left looking through manually trying to find which dirs didn't clone, delete them, re submodule update, etc. A script would probably be a far less error prone way to solve this.
the-mikedavis
changed the title
investigate using a script instead of submodules for grammars
investigate replacing the submodules system for grammars
Feb 15, 2022
Tree-sitter grammars are currently all added to the project as git submodules. There are quite a few supported languages now, so it ends up being very expensive to clone helix.
It may make sense to have a separate CLI to do fetching and grammar compilation in the future, but for now it looks like a nice and small increment to switch submodules out for a script like this one in tree-sitter itself. A shallow clone for each grammar would be faster.
There are also some packaging methods that have a hard time with submodules which a script may improve. See void-packages#33881 and #1448.
The text was updated successfully, but these errors were encountered: