apheleia VS emacs-overlay

For black, I can recommend apheleia. It handles not only black but also all the other common formatters (not only for Python), with custom ones being relatively easy to add.

1.projectile-kill-buffers or the built-in project-kill-buffers will do that for the current project. You could run that before switching projects.

2. https://github.com/radian-software/apheleia

3. There might be a way to do this but I'm not sure. Emacs being inherently single threaded probably makes this difficult. But yes, I use M-x (re)compile.

4. libvterm is the best still imo. You can definitely do multiple instances and there's even different tab modes in Emacs now.

I forgot to mention a third option namely lassik/emacs-format-all-the-code and there are efforts to combine/consolidate the three into a single package which would be great.

raxid502/apheleia

I use formatters in order to automatically format source code on save. Personally I use apheleia for this. It requires clang-tools installed as it uses clang formatter.

Generally speaking, emacs does only so much for indenting those mixed mode files, so you might want to use a dedicated JS(X)-formatter (default one would be prettier). I can recommend integrating it using apheleia. It automatically prettifies buffers on save, but without having your cursor jump around like prettier-mode does. It also relies on having the prettier script available (from npm i -g prettier or its likes).

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.