If there’s one thing I spend a good amount of time in, it’s my terminal emulator. Or shell. Or prompt. Whatever. For me, it’s konsole.
I write my blog posts, journal, chat with people and do a lot of my code editing from this place. Of course, some things I do in other applications like Firefox or an IntelliJ-based IDE1 but even then, those applications tend to have experiences tailored for a user who’s a bit like me: spending loads of time in Vim and swapping I/O between panes.
My leaning to Vim and tmux isn’t something of a religious thing - though I do
joke in that favor. It’s more so of a feeling of efficiency. I occassionally hit
ESC whilst in text entry fields on the Web out of habit - Vim uses that key to
denotate the exiting of the current editing state (INSERT) into one of its modal
Getting Them On My Machines
Alas, whilst working at Clef and side projects, the needed differences in my personal laptop’s configuration and my work machine has forced me to consider creating multiple sets of configuration for each one. Initially, I made use of a Bash-based framework for this but in my efforts to get a better understanding of Bash itself and the nuances between macOS and Ubuntu, I’ve removed it from my configuration and made my own.
The splitting away mentioned before led to a bunch of “smaller” repositories that I use for focused aspects of life. At the time of writing, the repositories that I have (all hosted on Github):
- dotfiles: Holds the core components.
- kderc: KDE-specific aspects.
- osxrc: macOS-specific aspects.
- vimrc: Vim-related files and configuration.
- gitrc: Git addons and base configuration.
- tmuxrc: Tmux-based configuration.
Each of these repositories are homes(h)ick-powered repositories. This allows me to run something like:
That command would clone and link the configuration stored in
$HOME directory. There’s a matter of unlinking files that hasn’t been
solved yet but for the moment, I have a few broken symbolic links that are
Getting My Language Tools In There