Dotfiles

User-specific application configuration is traditionally stored in so called dotfiles (files whose filename starts with a dot). It is common practice to track dotfiles with a version control system such as Git to keep track of changes and synchronize dotfiles across various hosts. There are various approaches to managing your dotfiles (e.g. directly tracking dotfiles in the home directory v.s. storing them in a subdirectory and symlinking/copying/generating files with a shell script or a dedicated tool). Apart from explaining how to manage your dotfiles this article also contains a list of dotfile repositories from Arch Linux users.

Tracking dotfiles directly with Git

The benefit of tracking dotfiles directly with Git is that it only requires Git and does not involve symlinks. The disadvantage is that host-specific configuration generally requires merging changes into multiple branches.

The simplest way to achieve this approach is to initialize a Git repository directly in your home directory and ignoring all files by default with a gitignore(5) pattern of *. This method however comes with two drawbacks: it can become confusing when you have other Git repositories in your home directory (e.g. if you forget to initialize a repository you suddenly operate on your dotfile repository) and you can no longer easily see which files in the current directory are untracked (because they are ignored).

An alternative method without these drawbacks is the "bare repository and alias method" popularized on Ask Hacker News: What do you use to manage your dotfiles?, which just takes three commands to set up:

$ git init --bare ~/.dotfiles
$ alias config='/usr/bin/git --git-dir=$HOME/.dotfiles/ --work-tree=$HOME'
$ config config status.showUntrackedFiles no

You can then manage your dotfiles with the created alias. If you are using Bash and would like bash completion for this alias, simply install bash-complete-alias^AUR, then add the alias and the following line to your ~/.bashrc.

$ complete -F _complete_alias config

Another way to get completion in bash is adding the following to your ~/.bashrc (taken from ):

source /usr/share/bash-completion/completions/git
__git_complete config __git_main

Tip: To avoid accidentally commiting confidential information, see Git#Filtering confidential information.

Host-specific configuration

A common problem with synchronizing dotfiles across various machines is host-specific configuration.

With Git this can be solved by maintaining a master branch for all shared configuration, while each individual machine has a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; when shared configuration is modified in the master branch, the per-machine branches need to be rebased on top of the updated master.

In configuration scripts like shell configuration files conditional logic can be used. For example, Bash scripts (i.e. .bashrc) can apply different configuration depending on the machine name (or type, custom variable, etc.):

if [[ "$(hostname)" == "archlaptop" ]]; then
    # laptop specific commands here
else
    # desktop or server machine commands
fi

Similar can also be achieved with .Xresources.

If you find rebasing Git branches too cumbersome, you may want to use a tool that supports file grouping, or if even greater flexibility is desired, a tool that does processing.

Tools

File grouping: How configuration files can be grouped to configuration groups (also called profiles or packages).
Processing: Some tools process configuration files to allow them to be customized depending on the host.

Name	Package	Written in	File grouping	Processing
chezmoi	chezmoi	Go	directory-based	Go templates
dot-templater		Rust	directory-based	custom syntax
dotdrop		Python	configuration file	Jinja2
dotfiles		Python	No	No
Dots		Python	directory-based	custom append points
dotter		Rust	configuration file	Handlebars
dt-cli		Rust	configuration file	Handlebars
GNU Stow		Perl	directory-based	No
Mackup		Python	automatic per application	No
mir.qualia		Python	No	custom blocks
rcm		Perl	directory-based (by host or tag)	No

Tools wrapping Git

If you are uncomfortable with Git, you may want to use one of these tools, which abstract the version control system away (more or less).

Name	Package	Written in	File grouping	Processing
dotbare		Shell ()	repository-wise	No
dotgit	dotgit^AUR	Python	filename-based	No
homeshick		Bash	repository-wise	No
homesick	–	Ruby	repository-wise	No
Pearl		Python	repository-wise	No
vcsh		Shell	repository-wise	No
yadm⁽¹⁾		Python	filename-based (by class/OS/distro/hostname/user)	Built-in templates/Jinja2/ESH (optional)

Supports encryption of confidential files with GPG or OpenSSL.

User repositories

Author	Shell (Shell framework)	WM / DE	Editor	Terminal	Multiplexer	Audio	Monitor	Mail	IRC	File Manager	RSS reader
alfunx	zsh	awesome	vim	kitty	tmux	ncmpcpp/mpd	htop/lain	thunderbird
Ambrevar	Eshell	EXWM	Emacs	Emacs (Eshell)	Emacs TRAMP + dtach	EMMS	conky/dzen	mu4e	Circe
ananthu	zsh	bspwm	neovim	alacritty		mpv	htop, polybar	neomutt	weechat	ranger
awal	fish	i3	vim	st	tmux		i3status		The Lounge
ayekat	zsh	karuiwm	vim	rxvt-unicode	tmux	ncmpcpp/mpd	karuibar	mutt	irssi
bachoseven	zsh	dwm	neovim	st		ncmpcpp	bottom	neomutt	weechat	lf
bamos	zsh	i3/xmonad	vim/emacs	rxvt-unicode	tmux	mpv/cmus	conky/xmobar	mutt	ERC
benmezger	zsh/bash	i3-gaps	emacs	rxvt-unicode/alacritty	tmux	mopidy/ncmpcpp	i3status-rs	mu4e/neomutt/mbsync	weechat
brisbin33	zsh	xmonad	vim	rxvt-unicode	screen		dzen	mutt	irssi
BVollmerhaus	fish	i3-gaps	kakoune	kitty			polybar			ranger
cinelli	zsh	dwm	vim	termite-git		pianobar	htop	mutt-kz	weechat
dikiaap	zsh	i3-gaps	neovim	alacritty	tmux		i3blocks			nnn
Earnestly	zsh	i3/orbment	vim/emacs	termite	tmux	mpd	conky	mutt	weechat
ErikBjare	zsh	xmonad/xfce4	vim	terminator	tmux		xfce4-panel		weechat
falconindy	bash	i3	vim	rxvt-unicode		ncmpcpp	conky	mutt
filiparag	fish	bspwm	vim	alacritty	tmux	mpv, playerctl	htop, polybar	mail-notification		pcmanfm
gardenapple	zsh	sway	neovim	kitty			htop	aerc
graysky	zsh	xfce4	vim	terminal		ncmpcpp	custom	thunderbird
hugdru	zsh	awesome	neovim	rxvt-unicode	tmux			thunderbird	weechat
insanum	bash	herbstluftwm	vim	evilvte	tmux		dzen	mutt-kz
isti115	pwsh	sway	neovim	alacritty	tmux	mpv / playerctl	waybar / htop / ytop			ranger
jasonwryan	bash/zsh	dwm	vim	rxvt-unicode	tmux	ncmpcpp	custom	mutt	irssi
jdevlieghere	zsh	xmonad	vim	terminal	tmux		htop	mutt	weechat
jelly	zsh	i3	vim	termite	tmux	ncmpcpp		mutt-kz-git	weechat
JonasDe	zsh	i3	vim	rxvt-unicode	tmux
Jorengarenar	sh/Bash	i3	Vim	xterm	tmux	mpv	htop	aerc	WeeChat	ranger	QuiteRSS
MarkusZoppelt	zsh	gnome	vim	terminal	tmux
maximbaz	zsh	sway	kakoune	kitty			waybar	neomutt		nnn
mehalter	zsh	i3-gaps	neovim	termite	tmux	cmus	gotop	neomutt	weechat	ranger
meskarune	bash	herbstluftwm	vim	rxvt-unicode	screen		conky		weechat
neersighted	fish	i3	neovim	alacritty	tmux	ncmpcpp
nimaipatel	fish	awesome	neovim	alacritty		ncmpcpp
oibind	fish	awesome	neovim	st	tmux		htop-vim		weechat	lf
OK100	bash	dwm	vim	rxvt-unicode		cmus	conky, dzen	mutt	weechat
orhun	bash	i3-gaps	neovim	alacritty			i3status		weechat	tere
pablox-cl	zsh (zplug)	gnome3	neovim	kitty
peterzuger	zsh	i3-gaps	emacs	rxvt-unicode	screen	moc	htop
potamides	bash	awesome	neovim	termite	tmux	ncmpcpp	conky,htop	mutt	weechat	ranger
reisub0	fish	qtile	neovim	kitty		mpd	conky
Scrumplex	fish	sway	neovim	kitty		ncmpcpp / pipewire	waybar	aerc		ranger
sistematico	zsh/fish/bash	i3-gaps	vim/nano	termite	tmux	ncmpcpp	polybar	mutt	weechat
sitilge	zsh	sway	neovim	alacritty			htop	thunderbird
thecashewtrader	Eshell	EXWM	Emacs	Emacs (VTerm)	Emacs	Bongo	htop	mu4e	ERC	Dired	Elfeed
thiagowfx	bash/zsh	i3	vim	alacritty	tmux	playerctl	i3status			ranger
tuurep	bash	openbox	neovim	alacritty	tmux		polybar
vodik	zsh	xmonad	vim	termite-git	tmux	ncmpcpp	custom	mutt	weechat
w0ng	zsh	dwm	vim	rxvt-unicode	tmux	ncmpcpp	custom	mutt	irssi
whitelynx	fish	i3	neovim	kitty			i3pystatus
whynothugo	zsh	sway	neovim	alacritty		mpv	waybar, top	neomutt		nemo
wryonik	zsh	i3-gaps-rounded	vim	terminator		cmus	htop, i3blocks, gotop			ranger, nautilus

gollark: I may be referred to as car/cdr if desired.

gollark: The problem with spaces is that you can’t actually see them. So you can’t be sure they’re correct. Also they aren’t actually there anyway - they are the absence of code. “Anti-code” if you will. Too many developers format their code “to make it more maintainable” (like that’s actually a thing), but they’re really just filling the document with spaces. And it’s impossible to know how spaces will effect your code, because if you can’t see them, then you can’t read them. Real code wizards know to just write one long line and pack it in tight. What’s that you say? You wrote 600 lines of code today? Well I wrote one, and it took all week, but it’s the best. And when I hand this project over to you next month I’ll have solved world peace in just 14 lines and you will be so lucky to have my code on your screen <ninja chop>.

gollark: Remove the call stack and do trampolining or something?

gollark: Yes, I think this is possible.

gollark: (ethically)