tree-sitter-langs VS emacs-overlay

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.

The project uses this overlay: https://github.com/nix-community/emacs-overlay

What that means is if something is broken in Emacs, the community will fix it, and all I need to do is run `nix flake update` to grab the latest commit and then `nix run .#build-switch` to alter my system. Easy.

Thanks for the heads-up on the 404s! I've fixed those links.

In re: to org-agenda, I don't use that as much anymore. But I heavily, heavily using org-roam w/ org-roam-dailies everyday to build my own networked graph of notes. For tasks, nowadays I just use simple docs for projects and Asana to keep a catalog of everything.

Im a newish NixOS user, Ive used it like 20 times before but always quit because I couldnt debug errors, trying not to give up for the 20th time this time lmao; so Ive been trying to learn how to use overlays & flakes for a couple of days now. The ones I want to use/enable are: - Emacs-Overlay - Spicetify-Nix

Nix offers the same advantage through the use of emacs-overlay. Besides, Nixpkgs contains more Linux packages than any other distros. Depending on the user's needs, Nix is another option.

You can use this overlay to get the latest https://github.com/nix-community/emacs-overlay

Depending on your goals, emacs-overlay is also worth a look.

{ pkgs ? import {} }: ((import (builtins.fetchTarball { url = "https://github.com/nix-community/emacs-overlay/archive/master.tar.gz"; })) pkgs pkgs).emacsGit

One option is to install Nix and use emacs-overlay.

You can install Nix on your mac and use https://github.com/nix-community/emacs-overlay/, which supports all the existing tree-sitter-based major modes OOB.

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more activity about Emacs configurations two-three years ago.

> Compile EmacsLisp files ahead of time

Ooh, this is interesting. Hoping to see a derivation in https://github.com/nix-community/emacs-overlay soon.

[0] I am not complaining though as Doom was the main author's personal config from the get-go. I am just pointing out a void.