Folding means that if stow discovers a parent directory for a project or a file
in it exists, it doesn’t create the directory structure and then links the file,
instead it makes a symbolic link between the directory.
This means that any files created in that directory show up in this repository.
The upside of that situation is that if I remove or rename files, and the
directory it’s in is folded, it doesn’t leave dead links around.
I’m very used to having M-up and M-down do the same thing as regular up and
down. In fish by default this prints the previous command, with ‘&| less;’ added
on.
Sometimes I’m too impatient and will try to start ‘emacsclient’ before the
server has finished starting up. This means that it will start another Emacs
session and it won’t be obvious to me. Now it’ll just fail to start
‘emacsclient’ and I can try again a few seconds later.
M4 treats ‘#’ as a comment delimiter, so that if there is a macro that expands
to, for example, ‘#222222’ it will ignore any macros any further along the line.
- Add xsession. Instead of requiring each of my machines to setup their own
‘.xsession’ add one that should work for all of them.
- Use M4 for the Xresources database. I didn’t want the X11 project to be aware
of all the configuration files that could be added in there and I was able to
figure out how to have it load all of the configuration files in the
‘Xresources.d’ directory. Now each configuration can inject properties into the
X resources database.
- Have ‘.xsession’ load all of the scripts in ‘.config/X11/Xsession.d’. Each
configuration can now inject some script to run when X starts.
- Have ‘.xsession’ load a machine-specific script so that each machine can
override what it does when X starts.