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
I finally saw your HN comment only ~1 year later 😅. While it would be possible to use Cursorless as a voice interface to edit Glicol code out of the box, if you want the ability to use rich scopes to manipulate the parse tree, the first step would be to write a tree-sitter parser. There are other benefits to writing a tree-sitter parser, as they're increasingly used to add rich language support to various editors (eg Helix, neovim, etc)
The text was updated successfully, but these errors were encountered:
Interesting. I am working on a collaborative editor using wgpu so I have control over rendering everything on the screen. This would be a good place to experiment with it.
I am also rewriting everything in pure Rust, without Pest and Petgraph, so I will try the tree there as well.
It's definitely not perfect (it has small errors on basically every file I try to pass in to it, but it gets most of the structure right), and it could be more granular (I was mostly only trying to implement it to get syntax highlighting with nvim-treesitter), but if others can submit PRs to make it work better, that would be much appreciated :)
I finally saw your HN comment only ~1 year later 😅. While it would be possible to use Cursorless as a voice interface to edit Glicol code out of the box, if you want the ability to use rich scopes to manipulate the parse tree, the first step would be to write a tree-sitter parser. There are other benefits to writing a tree-sitter parser, as they're increasingly used to add rich language support to various editors (eg Helix, neovim, etc)
The text was updated successfully, but these errors were encountered: