Tree sitter support

[BrownNPC]

The current tree sitter grammar for this language has licensing issues and bugs. This prevents support from being added in the Helix editor. helix-editor/helix#15061

Since the Umka tree sitter repo does not have a license. Helix cannot redistribute the grammar either.

[vtereshkov]

@BrownNPC What tree sitter repo do you mean? I personally don't maintain any.

[thacuber2a03]

@BrownNPC yeah I'm the supposed "maintainer" of the tree-sitter parser... about that...

1. I didn't think it didn't have a license, I probably didn't add it because I forgot or it wasn't done, which brings me to

2. it's not done. it's lacking tons of features and that's from my inability to resolve the grammar conflicts inherently present in Umka as I don't have enough experience with tree-sitter. besides, I don't even know the groups used by Helix to highlight; I was suggested by @ske2004 (cc) to use the Textmate scope names, but I'm not sure if Helix uses those. in the current state of the parser, I would actually recommend not using it, more so seeing as Helix is a "production" project and I started the parser as a "test"

sorry for the inconveniences, and I'll add a license to the repository later, MIT for now, but I think this issue should've been reported in my repository, not here

regards xnk

[BrownNPC]

In the future, Umka could maintain it's own tree sitter parser perhaps? The license itself is not the main issue. I opened this issue to highlight that Umka needs a complete tree sitter parser for better editor support

[vtereshkov]

@BrownNPC I'm not planning this, as my resources are limited. You can ask @thacuber2a03 or @ske2004 if they would like to resurrect that old project and maintain it.

[ske2004]

@BrownNPC Sadly I tried many times and I failed... There were 2 attempts aside from this one. It's really frustrating to write Treesitter grammar. I'm hoping eventually someone will come along and make a working one.

[thacuber2a03]

@ske2004 honestly wouldn't blame you, Umka's grammar is rather ambiguous without typechecking