makem.sh VS chemacs2

Well, for one thing, restarting Emacs to reload libraries gets old. This command helps. Also, this script eases testing in clean Emacs configs outside of one's main editor. Then, of course, tools like Elpaca seem to be the next generation...

Anyway, as Nic said, any package maintainer who cares will want to fix those warnings. I use my own makem.sh tool to lint compilation warnings before publishing.

This is one of the reasons I wrote makem.sh. I recently added makem.el to the repo, which is an Elisp library that provides a Transient menu to make using it very easy (you don't have to use M-x compile or a shell).

See also https://github.com/alphapapa/makem.sh, which is much simpler to use.

Wow, finally! And just when I've gotten the bugs ironed out of with-emacs.sh and makem.sh related to Emacs 28's changes. Well, pre-29 versions will still be around for a long time, so with-emacs.sh will remain useful, but it will be nice to have support for this integrated into Emacs.

Reported one: https://github.com/alphapapa/makem.sh/issues/35

FYI, see also evenp. :) Also, this may help you lint and test your packages: https://github.com/alphapapa/makem.sh

I generally recommend using makem.sh to lint, because it can test in a clean Emacs configuration using a variety of tools, and it works with compile, so you can just press g to rerun it. It will warn you about things like un-prefixed cl functions.

For general packaging, package-lint will catch many dependency issues. I run it with https://github.com/alphapapa/makem.sh

You could manage such a system with tools like Chemacs, https://github.com/plexus/chemacs2

Edit: Actually this may be what you want: https://github.com/plexus/chemacs2

https://www.spacemacs.org/ is a layer on top of emacs that solves a number of shortcomings including a more modern UI. If you use https://github.com/plexus/chemacs2, you can always run emacs and spacemacs independently, both for learning, troubleshooting etc.

have a look at how https://github.com/plexus/chemacs2 does this sort of things.

I asked this same question a year and half ago and since that post I started reading Mastering Emacs by Mickey Petersen which was really helpful, I used Chemacs to keep my evil config around in case I give up. But I ended up dropping that config and I realized I wasn't really into modal editing. It took me one month to get used to my new config but that was worth it, everything in Emacs became consistent.

Perhaps the biggest game changer in my new init file is chemacs2. This allows one to choose one among many possible ".emacs.d" directories to use for the emacs that is being invoked.