fix jetbrains windows. change float_rules from a dictionary to a list of Match items, because the dictionary feature was finally removed and i couldn't be arsed to sort it out based only on a warning :)
picom appears to be making firefox unstable for the time being. i like firefox better than picom and don't feel like digging into it just now.
fix font. improve jetbrains dialog behavior.
This is a place for me to bounce dotfiles from machine to machine.
They're probably too customized to my personal preferences to be much good for others, though the 2021 re-org should make that less true than it used to be.
For 2021 my main systems are Arch or Manjaro based, so naming conventions and organization may reflect that a little bit.
This repository is intended to be used with GNU Stow.
GNU Stow is a symlink farm manager which takes distinct packages of software and/or data located in separate directories on the filesystem, and makes them appear to be installed in the same place. For example,
/usr/local/bincould contain symlinks to files within/usr/local/stow/emacs/bin,/usr/local/stow/perl/binetc., and likewise recursively for any other subdirectories such as.../share,.../man, and so on.This is particularly useful for keeping track of system-wide and per-user installations of software built from source, but can also facilitate a more controlled approach to management of configuration files in the user's home directory, especially when coupled with version control systems.
To install any of these configurations on a system, first obtain stow from the OS package manager (pacman -S stow on Arch) then clone this repository into your home directory. From within this repository run stow <application> and the configuration files from this repository will be installed into the parent of the directory where the repository is checked out. If you don't want to clone into your home directory, run stow with --target=${HOME}
To add a configuration to the repository, create a directory named for the application in question, then reproduce the directory structure it requires under ${HOME} and move any of its configuration files into that structure. Run the command stow <application> to install symbolic links back into home. Then git can be used to track changes to the configurations over time and to (more easily) bounce configurations from machine to machine.
Anything here that's mine is available under the MIT license. Anything specific I copy and stash here will be credited below.
The general ideas here came from some combination of configurations I've been transferring from machine to machine in a much less organized way for years, fond memories of using ratpoison on Slackware in the early '00s, and looking at some of the setups shared on /r/unixporn.