configurations and the like
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
katherine 86a2ff3916 easier to just use the plugin i guess 3 months ago
.config typo 3 months ago
.vim easier to just use the plugin i guess 3 months ago
.zkbd urxvt -> alacritty 4 months ago
.Xmodmap misc 6 years ago
.Xresources explicit fcitx input for urxvt 1 year ago
.gitmodules submodule url 4 months ago
.iex.exs add rpass func 1 year ago
.mailcap use lynx for html mail over w3m 2 years ago
.muttrc add pgp support for mutt 3 years ago
.ocamlinit synchronise common prompts 3 years ago
.utoprc ocaml support 3 years ago
.vimrc easier to just use the plugin i guess 3 months ago
.xinitrc revert to old fcitx 9 months ago
.zprofile urxvt -> alacritty 4 months ago
.zprofile-abduco add curses session-switcher 1 year ago
.zshenv move envars to .zshenv where they belong 3 years ago
.zshrc urxvt -> alacritty 4 months ago
.zshrc-freebsd clean zsh stuff 2 years ago
.zshrc-linux merge tablet configs 3 years ago
.zshrc-linux-desktop encrypted mount 3 months ago urxvt -> alacritty 4 months ago


desktop configurations. function over form, though things being pretty is nice


clean dirty


.config/init/ contains vars, a file defining shared variables for the desktop which are sourced and used elsewhere. these settings can be overridden by creating a "voverride" file in the same directory. .config/init also contains a series of "gen/*.sh" files, which create configuration files in $tmpdir so programs not configurable via shell scripting will automatically match the current settings as well. i stick symlinks to the $tmpdir version where they would normally be. also included are folders "funcs" and "funcreqs", which, respectively, contain executable scripts and their prerequisite commands and arbitrary check commands. the latter prerequisites are tested from .zprofile at login and, if passed, the functions are symlinked into $tmpdir/funcs, which is appended to $PATH. thus, this system allows for configs which automatically adapt to the host environment, enabling only what functionality is compatible.

Current Utilities


using nvim, but no big incompatibilities with base vim yet with the way i use it, so falling back works fine. have a few fun things, including auto-loaded, filetype-specific settings and basic templates, a few fancy mappings, and a simple 16-colour colourscheme. take a look at muh .vimrc for details and things.


herbstluftwm has the really interesting concept of allowing manual tiling of frames and then providing automatic layouts for inside those frames. in theory, it's the best of both worlds, but it gets kind of confusing, so i've just set the layout to always be max. this way frames basically just have multiple tabs for me that can by cycled through. it's really neat for saving screen space! (try splitting a screen with both an editor and a terminal on one side and all your documentation on the other). i3 can do much the same thing, but it comes with lots of slightly annoying things to get rid of.


urxvt-perls suddenly stopped working, so switched to alacritty. few keybinding issues to get around, and font rendering isn't great, but it works


both are fantastic for keyboard-driven file management. i've forked sxiv to use 4 colours rather than 2, to better fit the theme, but still've got to figure out how to write a ranger extension that can receive selections from sxiv, because squinting at filenames is just bleh. python is my bane, though...


a nice password manager-a-ma-bob, gpg locked and easy to sync with git. there's a firefox addon, but it doesn't really work, and there's an existing dmenu frontend, but it's not very featureful, so i wrote my own.


useful things all around. i've "patched" dunst (really just a very bad hack) to auto clean up on-screen messages when notifications are received from and, which makes things update cleanly in-place if a key is repeatedly pressed. hopefully this sort of functionality will be added properly, but the documentation is sparse and don't have the time to figure out how right now x-x


input is messy, but fcitx seems like the most functional out there at the moment. fcitx-mozc a nice.