New Parser is in Alpha Version

[jpt13653903]

My apologies for the duplicate announcement, but it would seem as if the only way to detach a fork is to create a new repo, which is what I've done. The old fork will live on for a short while here, but I plan on deleting it in due course.

Alpha Version

I'm excited to announce that I think the new parser (with highlighting script) is ready for alpha-testing.

It "should" be able to successfully highlight anything the base VHDL 2019 standard can throw at it. I have not implemented PSL and VHPI, because I believe that those should be extensions that are not part of this repo.

Installation Instructions

See the readme for installation instructions in Neovim. I'm not sure about Helix and others.

Help required

Testing

I need help testing. Please feel free to fork the master branch and add some test corpus and highlight files. Just comment below that you're doing so and I'll go grab them directly from your repo (by adding an additional git remote).

I'm also intending this discussion as a general-purpose bug-reporting place until we can move it out of alpha into a beta version.

Queries

I've populated a preliminary highlights.scm. Feel free to fork the repo and contribute -- I'll grab updates directly from there as described above.

I need someone else to do the folds.scm, context.scm, etc. because those are not features I use.

Named Grammar Nodes

I'm open to suggestions related to grammar nodes and tree organisation. Please post your recommendations below and I'll update. You can of course also issue a pull-request from your fork, but I think it might be easier if I take ownership of the tree structure.

Parser Size

I've fought the parser down from over 13 MB to the 6.5 MB that it is at the moment. Any suggestions on slimming it down further will be appreciated.

Timelines

I'll be mostly AWOL for the next 3 to 4 weeks due to other commitments, so please don't expect prompt responses. I'll pick it up again afterwards.

Historic Discussion References

• alemuller/tree-sitter-vhdl
• nvim-treesitter

FYI List:

• @dstadelm
• @richjyoung
• @SethGower
• @Chris44442
• @superzanti
• @clason
• @amaanq

[superzanti]

Again, I've got folds.scm and context.scm covered.

[jpt13653903]

Can I pass indents.scm also your way?

[superzanti]

Sure thing. I'll make a push mid or late next week.
Work just picked up so I haven't had as much time to work on this.

[jpt13653903]

Awesome -- thanks!

[Chris44442]

Very nice! I like the simplified grammar from what I can tell so far. I will start using this as my daily driver right now and report any issues.

[jpt13653903]

I'm also using it as my daily driver, and updating as I find issues...

[jpt13653903]

I'm changing workflows...

I've changed the repo branch structure to run a more structured workflow:

• master contains the latest, and tested, features (I'm not running versioning yet -- I'll start that once the alpha-testing is complete)
• develop contains the latest, greatest features and updates, but might not be fully tested yet.
• feature/..., bugfix/..., etc. might or might not work. Consider these work-in-progress.

What this means for you:

• When issuing a PR, please base in onto develop.
• Call your branch whatever you like -- I'm not going to enforce traditional feature, bugfix, etc. prefixes, because I've found them too restrictive in the past, but it would be nice if you prefix your branch name with something sensible.
• As a contributor, you might want to point your Neovim (or other editor) config to use the develop branch.

[jpt13653903]

The new parser is nearing completion, and I'll probably call it "version 1.0" and issue the nvim-treesitter PR by this weekend.

I'm therefore closing this discussion. Feel free to open up issues and more discussions if / when you'd like to see something improved.