I'm working on moving my build setup to my own laminar[1] instance. To do this I
need to be able to package files up. It appears that I couldn't quite get Cask
to work, and Eldev exists in the Guix[2] package repository.
[1]: https://laminar.ryuslash.org/
[2]: https://guix.gnu.org/
‘paredit-mode’ appears to have added keybindings for ‘C-j’ and ‘RET’ that
weren't there before (or did I enable ‘paredit-mode’ in IELM recently?) and that
interfere with executing code.
This way of removing the keybindings works in a buffer-local only way so that in
other buffers the ‘RET’ and ‘C-j’ keybindings remain untouched.
It's a fun idea, but practically it makes things a lot slower in certain
situations and by default it has some weird concepts of what safe or pure
functions are.
Loading ‘yasnippet’ shouldn't automatically load my package configuration. If my
package configuration hasn't been loaded it shouldn't try to include my snippets.
The big downside of usuing these cookies to inject my configuration into the
loading of a package is that it means that I can't load that package without my
configuration anymore. This means that when I start ‘emacs -Q’ and then call
‘package-initialize’ it'll load my configuration as well. This makes debugging
things very difficult.
The dependencies are also in the package files themselves and are the actual
source of truth. The way I’ve reorganized the stages should mean that this isn’t
necessary anymore.
In order to support my tablet which seems to have a lower maximum integer
value (I guess it’s 32-bit? I’m surprised) and can’t handle the version numbers
I was using before. It would turn them into floating point numbers, which adds a
~.0~, this made it impossible to install any package.
Any installations I have will need to reinstall all their oni packages so that
the new version number is picked up, since the new version number will be lower
than the old one.
