||3 years ago|
|.config||3 years ago|
|.vim||3 years ago|
|.zkbd||8 years ago|
|.Xmodmap||6 years ago|
|.Xresources||6 years ago|
|.gitmodules||5 years ago|
|.iex.exs||4 years ago|
|.lambda-term-inputrc||4 years ago|
|.mailcap||3 years ago|
|.muttrc||3 years ago|
|.ocamlinit||4 years ago|
|.utoprc||4 years ago|
|.vimrc||3 years ago|
|.xinitrc||3 years ago|
|.zprofile||3 years ago|
|.zprofile-dtach||3 years ago|
|.zshenv||3 years ago|
|.zshrc||3 years ago|
|.zshrc-freebsd||3 years ago|
|.zshrc-linux||4 years ago|
|.zshrc-linux-desktop||3 years ago|
|README.md||3 years ago|
desktop configurations. function over form, though things being pretty is nice
.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
.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.
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.
has some quirks, but still nothing else out there with the same functionality. check out urxvt-perls.
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 mpc-status.sh and pvol.sh, 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.