||2 weeks ago|
|.assets||2 years ago|
|.githooks||5 months ago|
|bootstrap||3 months ago|
|desktop||2 weeks ago|
|disks||3 years ago|
|git||6 months ago|
|multimedia||2 weeks ago|
|nvim/.config||2 weeks ago|
|office||2 weeks ago|
|pass||1 year ago|
|qutebrowser||2 weeks ago|
|scripts||2 weeks ago|
|services||5 months ago|
|sh||3 months ago|
|social/.config||2 weeks ago|
|ssh||1 year ago|
|terminal||2 weeks ago|
|writing||3 months ago|
|.gitignore||6 months ago|
|.gitlab-ci.yml||2 years ago|
|.gitmodules||5 months ago|
|.stowrc||3 years ago|
|LICENSE||5 months ago|
|README.md||3 months ago|
|install.sh||5 months ago|
Note that the below screenshots still show the X configuration from v0.1 which is very old by now. The current dotfiles are geared toward wayland for which the setup looks similar but not identical to the previews below.
What's in these dotfiles
- vim configuration for simple programming tasks (especially go/typescript/python/bash) and prose
- academic workflow tools, to allow quick citation, pdf compilation, and preview
- simple, efficient waybar with package update notification, and spotify (mpris) integration
- tmux session management through
- tmux fuzzy-searching of terminal sessions to switch to with hot-key (
<C-A><C-s>) in addition to normal session switching
- system-wide color management (terminals, vim, qutebrowser, polybar, xresources) through
flavoursapplication using base16 themes
- quick theme switching by activating
flavoursand fuzzy-searching themes with hot-key (default
- many vim color-schemes with quick light/dark switching (
F8) and individual theme switch (
- quick directory jumping using
fzf-like integrations for bibtex citation, vim buffer management, most recently used switching, shell command history, and more
The dotfiles use
GNU stow to link themselves in the home directory. You can clone this repository anywhere (though I have mine in
~/.dotfiles as it seemed most logical for me).
I would recommend doing an initial
git clone --recursive for this repository, since it contains git submodules, which will then automatically get pulled in as well.
Of course, you can do it non-recursively and then just pull those modules selectively which you actually want.
Once in the repository directory, when you then run
./install.sh it will install many of the packages I use (though they are probably slightly out-of-date) and link the dotfiles into the home directory.
I would mostly recommend this on fresh machines or a test machine first - it will link my personal dotfiles and, if you allow it, will install quite a few packages.
By default it will ask your consent for some steps -- use
./install.sh -f to force yes to everything.
The dotfile installation procedure is based on
stow, it will not overwrite anything already in the home directory (though you can force it to if you really want, using
stow --override='.*' -- I do not recommend this).
NOTE The same non-destructive installation procedure does not apply to the package installation and system setting file linking, where it can potentially overwrite or remove existing files.
After all files are linked and you open a new shell session, the
dotlink alias will allow you to re-link all dotfiles from anywhere on the system.1
Both automatic installation paths are presumably somewhat brittle. In any case, I would suggest to manually look through the files for things you want instead of copying and activating everything. Dotfiles are too personal to be standardized like that. They're pets, not cattle. Enjoy!
wayland- Containing basics for fully functional tiling wayland setup:
wezterm- Terminal emulator (fast, understandable and lua configurable)
tmux- terminal multiplexer (slowly migrating away in favor of wezterm)
nvim- Neovim configuration
vifm- vim-like file-manager
qutebrowser- vim-key enabled web browser
pass- Password management suite
bibtex- LateX/BibteX/pandoc plaintext writing & reference suite
git- distributed version control system.
office- office/productivity software for writing e-mail and setting appointments
- Generally, most configuration for applications attempts to follow the XDG specifications, keeping configuration in .config directory and supplementary files in .local/share directory. Over time, I am moving more applications to this standard: it keeps the home directory clean, and the separation of configuration, binaries, and data relatively clear.
zshdirectory contains all setup for the z-shell, my daily work environment. It should not be required for working with any other module but will add additional functionality to many (such as command auto-completion and so on).
shsets some base functionality for any shell you may wish to work in. It is, for now, the only module that is required for some other modules to work.2
roficontains additional scripts and a simple theming framework for rofi and should probably be reorganized to put the correct files into the correct directories (per xdg) at some point.
shmodule scripts are requirements for other scripts,
scriptsmodule contains most executable user scripts. Most of these have been migrated to other corresponding modules (e.g. if a script exclusively targets git functionality, it will live there), some useful --- or left-over --- stand-alone scripts remain however.
.local/share/pandoccontains configuration for academic latex writing (pandoc, really) and is of interest if you want to use this functionality.
.xinitrcis used for x initialization and program startup. At some point, some of the consistently running applications may be moved to systemd/runit as supervised services.
- Generally, top-level directories starting with a . are only meaningful for the repository not for the functionality of the machine that these dotfiles are deployed on. That means
.stowrcand similar files and directories will not show up in the final deployment in any home directory. Perhaps they should be called dotdot-files since they're the dotfiles for my dotfiles. 🙂 (Also, 'dotfiles'.)
This alias only works when the dotfiles are cloned into
~/.dotfiles, mirroring my setup. This is due to a hard-coded cd into this directory. If your dotfiles lie in another directory and you want to use the dotlink alias, simply change the corresponding line in
I may remove this requirement in the future to make modules more self-contained. However, relying on some base utility scripts makes it easier to avoid duplicating such functionality for each individual script in other modules. ↩︎