When I was relying on my external package channel I ended up with a conflict
being unable to upgrade a personal package because an issue with a Guix package
was preventing me from upgrading Guix itself.
These packages were installed in my default profile using ‘guix package -i’.
Since I'm using Guix home the setup of my default profile is a bit odd at the
moment, so since these seem to be here to stay for the moment I figured I should
install them in my home profile.
Use this option to specify that anything containing “(Meeting) | Microsoft
Teams” (which should be in the title of MS Teams when in a meeting) should have
100% opacity, and also that anything containing “freerdp” should have 100%
opacity.
For Teams I really only need it to be opaque once a meeting starts, I don't care
the rest of the time.
For XFreeRDP I've tried matching on ‘class_g’, ‘name’, nothing seems to work.
Using ‘opacity-rule’ finally seems to have an effect.
The rules both use ‘*’ to match anywhere in the name, and ‘?’ to specify that
the match should be case-insensitive.
The previous version of the configuration was complaining that my ‘config’
section was not a valid value for the ‘package’ section. I didn't quite
understand why it would complain about that, so I decided to use my now improved
Guix Home knowledge (compared to when I copied the previous version) to just
rewrite the service in a way that matches my other services.
This also includes an attempt at installing a custom SCSH that defines some
search paths. But unfortunately it didn't work, so the SCSH ends up being the
usual one and the ‘mpd-random-albums’ package doesn't actually work.
The main MPD configuration does work, though.
This also includes the instruction to install tmsu which I want to try out
again.
- Sort all use-module directives
- Remove ‘gcc-toolchain’ from the installed packages because it appears that the
regular emacs-next (not from a git checkout) works fine without it.
- Add ‘emacs-org-roam’ and ‘emacs-vterm’ packages because they both come with C
modules and installing them on-the-fly in Emacs wasn't working properly.
- Add ‘fakeroot’ package because it appears to be needed now that I'm using
guix-home if I want to build packages for Archlinux. This still happens when I
need to install some proprietary program from the AUR.
- Add an Emacs configuration service. For now this just ensures that the
‘emacs-next’ package is installed and creates a shepherd service that starts
Emacs when I log in.
- Change the default run dialog from ‘rofi -show run’ to ‘rofi -show drun’ to
run .desktop files. This offers more control over what does and doesn't show
up in the list and allows me to put only stuff in there that actually works in
a graphical environment.
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’
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.
Even though the output of the ‘--help’ command promises that ‘--file-guile’ is
the same as ‘-fg’ it appears that specifying ‘--file-guile’ doesn't work. It
just pops up the help message.
The herbstluftwm configuration isn't complete yet, it's only the package so far,
but it does extend the xsession service to include a line in xsession to execute
the window manager in a bit of a hacky way.
This also adds a ‘mixed-executable-file’ function which is the same as the
‘mixed-text-file’ except that it also sets the executable bit for the computed
file.
