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.
There are multiple versions of the gnupg binary available on Windows. One from
MSYS2 and one from Cygwin at the very least. And which one works is heavily
dependent on the rest of the system configuration and the way Emacs is
installed.
This should revert it back to ‘nil’ when I start Emacs. I can’t use
‘package-quickstart’ because it will cause an error on startup and then my Emacs
daemon doesn’t work. I’m in the process of moving over to a different way of
loading my Emacs packages anyway, so I’ll see if it’s still useful after that.
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.
It’s possible that someone enters a URL that isn’t part of the
‘package-archives’ variable. If the name entered doesn’t correspond to a name in
‘package-archives’, use it directly, assuming that it was a URL that was
specified.
Typos are too easy having to type in the ‘archive-url’ argument every time on
its own. Since you’re probably posting to an archive that you also use, reading
from the ‘package-archives’ seems appropriate.
