It's me, your weekly #emacs rambling birb

[farcaller@hdev.im]

It's me, your weekly #emacs rambling birb.

Today I am going to rant about tree-sitter and emacs and consult and vertico and why the hell is my `consult-buffer` taking SIX seconds to go to the next file.

So good news, if emacs is sluggish, you can `M-x profiler-start`, reproduce the problem, and `M-x profiler-report` to see where it's taking its sweet time. My problem is that the sweet time is in `treesit-auto--set-major-remap`.

https://www.masteringemacs.org/article/how-to-get-started-tree-sitter highlights one solution: you can manually remap every major mode to a TS-compatible mode.

I'm pretty sure that the culprit is somewhere in https://github.com/renzmann/treesit-auto, but the workaround from https://github.com/renzmann/treesit-auto/issues/84 doesn't seem to fix the problem for me.

Oh well.

I find it peculiar that I very much switched non-programming editing to emacs by now (org, md, yaml, all that stuff), but I still use nvim for code because nvim is just *fast*. It's like everything in it is just more efficient whereas emacs is fancy but takes its time (I'd say that my barebones emacs setup is on par with VSCode in slowness). With vim, I don't think if I need to do anything to open some extra random file type, it will most probably just work, and the only thing that gave me a headache recently was pkl support.

[crandel@fosstodon.org]

@farcaller I was right to not use treesit-auto at all