tree-sitter-langs VS doomemacs

I just had a quick look at tree-sitter-langs to double check its TypeScript support. And seems to have a full set of highlight queries for it.

I use script/compile swift from 'tree-sitter-langs' to build the grammar on both M1 and x86 machines. But I was looking at that code yesterday and I actually can't figure out why it works to produce an arm64 dylib for me. There's no place where the target arch is being set. It's very odd.

However, there are no queries available for it to highlight csharp: https://github.com/emacs-tree-sitter/tree-sitter-langs/tree/388dcbbc237b2b1360e5b148e67b158eecede805/queries

I've forked tree-sitter-langs with https://github.com/kiennq/tree-sitter-langs that can be used to convert from the current emacs-tree-sitter syntax to the built-in treesit's syntax. Based on https://github.com/emacs-tree-sitter/tree-sitter-langs/pull/99.

Those grammars are collected in the tree-sitter-langs repo, or you can build them yourself. I assume they're not bundled with Emacs yet, even on the feature branch. I don't know how the Emacs tree-sitter branch expects them to be registered and associated with a language mode, though.

The "essentially" qualifier is just because of the tree-sitter issue I was mentioning earlier which is just that this 3rd party package does not ship binaries built for FreeBSD. Everything else has worked exactly the same as on Linux.

Now I am speculating, but I think it would take less work to go through tree-sitter route. Seems that emacs tree-sitter repo already supports Elixir. And then we would need to write Elixir specific queries for combobulate, which supports incremental selection à la expand-region.

Yes, you need to install Emacs. It is probably available from whatever package manager your system uses.

I prefer Doom (https://github.com/doomemacs/doomemacs) to Spacemacs. However I haven't looked at Spacemacs for many years; perhaps it's now on par with Doom.

Ever since I've started my Emacs journey it seemed like the wholy grail to have your own (vanilla!) configuration without any hard dependencies on frameworks like Doom or Spacemacs. There are plenty of dotemacs configurations ouf there which can serve as a great source of inspiration.

Use doomemacs for a start. It really optimizes startup time and offers vast included modules as well as great package management. https://github.com/doomemacs/doomemacs/blob/master/docs/gett...

I installed Corfu using this PR in doom https://github.com/doomemacs/doomemacs/pull/7002

The doom documentation does a pretty good job of walking you through this: - https://github.com/doomemacs/doomemacs/blob/master/docs/getting_started.org - https://noelwelsh.com/posts/doom-emacs/

I was poking around and opened up the README.org file in the Doom Emac's faust module and i saw these nifty nagivation things that weren't coming form within the file. I didn't see anything in the directory that hinted at it (to me) either.

I tried this code: $ git clone --depth 1 https://github.com/doomemacs/doomemacs ~/.config/emacs ~/.config/emacs/bin/doom install

I am a long-time Emacs user and used to maintain my own config, but I switched to Doom Emacs [1] a year ago. Doom Emacs is like a pre-packaged/pre-configured emacs distro. You still need to configure the features that you want to use, but it's a lot easier (and faster) than having to do everything from scratch, and definitely if you already have some emacs background anyway. For me, it makes the newer, more advanced, features more accessible. Since switching, I started to use Emacs more again.

[1] https://github.com/doomemacs/doomemacs

Try an emacs distribution and see if you like it:https://github.com/doomemacs/doomemacs