I ran into some go code that use build tags. My existing test functions didn't work. To handle build-tags, I defined go-build-tags in .dir-locals.el and used the variable in my functions.
Today I learned and practiced using Pikchr. Pikchr is a low-level diagram markup language. This is my second attempt at it and I think it clicked this time.
The program is available is a single function library and a CLI that emits SVG.
@holgerschurig I don't have much experience with graphviz but I had similar problem with Mermaid. Pikchr does give you more finer control over layout with the trade-off of complexity.
I think the whole treesitter train passed me. Having separate ts major modes for every major mode, that are not derivates any more, makes configuration complex.
I'm not sure if the advantages of treesitter merit the complexity that was introduced into Emacs with this.
Some treesitter modes don't support certain features and I have constantly switch modes.
Perhaps I'll remove treesitter completely for now as I don't see any gains for the moment.
What are your experiences? What features do you get out of a specific treesitter mode that are not available in non-treesitter modes?
@louis For me, I was able to drop the go-mode from MELPA and use built-in go-ts-mode. It does lack some features like functions for running Tests, etc but I was able to chain together some custom functions very easily using the Treesitter functions. I've also enabled it for Python and haven't faced any problems so far.
For the Lisp modes (Guile and Elisp) I don't feel the need to use Treesitter.
