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.
Since the ‘set-face-attribute’ function documentation says that if you use ‘nil’
as the FRAME argument, you set the face attribute for all current and future
frames. However this doesn’t seem to work for my setup at all, the variable
pitch font is still “Sans Serif” when I open the first frame.
Since the functions called in ‘oni-gui-setup-faces’ work on either the given
frame or, if given ‘nil’, all future frames, it shouldn’t be a problem to call
it when the Emacs daemon is starting. And since my main org file is loaded
before a frame is created, it doesn’t use the right font otherwise.
Instead of setting the fontset things immediately always, check if we’re running
as a daemon and if so, delay setting the fontsets until after a frame is
created. This will set the fontset for each frame individually.
Tweak the font size of the Font Awesome icons to fit better with the rest of the
fonts.
Apparently in the docker container that’s running the tests, reading from the
command-line makes it a multibyte character (105 776 127 130), but defined in
Emacs it’s a unibyte character (61442). This might have something to do with
UTF-16 vs UTF-8?
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.
Move `scroll-bar-mode' to `oni-gui` because it isn't defined in the
non-GUI version. Fix the warning that `tool-bar-mode' wasn't
guaranteed to be defined by requiring the `tool-bar' library.
