- Put ‘userChrome.css’ into the ‘src/’ directory and have stow ignore any such
directory.
- Dynamically find the name of the default firefox profile.
- In case the firefox profile can't be found, output some messages stating such.
- Update the ‘userChrome.css’ as used by Firefox.
This is a temporary fix. I've switched from using ‘@theme’ to ‘@import’ because
the former discards the default theme, and apparently my theme makes some
assumptions about the state of things and requires the default theme to work.
The proper fix would be to fix my theme instead.
This change also fixes a bunch of typos and fixes the use of references within
the theme. References aren't strictly necessary, but my current theme relies on
them and they are technically a valid part of the configuration.
These configurations were set up wrong, putting the configuration files in
‘config/*’ instead of ‘.config/*’. The
‘home-xdg-configuration-files-service-type’ takes care of putting them in the
right directory.
I didn't know about this service before, it doesn't show up when I ‘guix home
search home’
The disc number is actually already included at the start of the ‘TRACKNUM’
field, so adding it to the ‘OUTPUTFORMAT’ setting explicitly just doubles it.
This means that with it specified calling abcde like this:
abcde -W 1
Would result in a file name like ‘1101 - something.ext’
Adding this package with the necessary dependencies makes sure that if it's
installed its dependencies are installed as well and everything should work.
Archlinux doesn't specify a value for this and relies on applications knowing
the default. Guix adds values to this list, meaning that because there is no
value initially it overrides the defaults completely. One thing that always goes
wrong when this happens is that Firefox installed through ‘pacman’ won't be able
to find some schemas it needs to show the upload file dialog and crashes when I
try.
The ‘syncthing-gtk’ program doesn't seem to start the syncthing daemon
automatically. In fact trying to start ‘syncthing-gtk’ through shepherd doesn't
seem to want to work at the moment, complaining that it can't close a bunch of
file descriptors.
The example was using a system constructor with a kill destructor, but I don't
think those two work together. I prefer having the application run in the
foreground and using the shepherd way of forking so I have more control.
I thought that ‘syncthing-gtk’ was a program that would fork (given the fact
that it has a ‘--quit’ command), but it turns out that it doesn't. Using the
system constructor means that shepherd will block until ‘syncthing-gtk’ is
closed.
