compat VS emacs-overlay

With the Compat library you can use define-keymap right away in your packages. See also my post about Compat.

Exactly, I think printing a loud warning is a perfectly acceptable solution. The note should ideally tell the user to ensure that dependencies are met. It makes sense to teach users a little better about the limitations of Straight or Elpaca with respect to dependency handling since I've seen many reports across the ecosystem where people didn't properly update dependencies. I usually bump dependencies when I really need new functionality. In particular with our Compat package, versions are meaningful and should be respected.

Compat co-maintainer here. Thank you for writing this post! One minor correction: Compat supports Emacs 24.4 and newer. Please link to the upstream repository at https://github.com/emacs-compat/compat instead of the Straight mirror, since the mirror does not preserve the Git history.

As /u/usaoc said, ensure-list can be used for this purpose - I use it all the time in my packages. I recommend to take advantage of the Compat package from GNU ELPA, such that you can use all new Emacs APIs even in packages targeting older Emacs versions. I am the maintainer of Compat. See also https://www.reddit.com/r/emacs/comments/10iep0o/compat_29130/ for more background.

I released version 29.1.3.0 of Compat, the Elisp forwards-compatibility library on GNU ELPA. This library may be interesting for you, if you want to use newer Emacs developments in your packages without breaking backward compatibility with older Emacs versions.

I updated some packages which included updating the dependency compat.el to 28.1.2.0

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.