This repository contains dotfiles, i.e. configuration files usually located in the home directory.

2016, Georg Sauthoff mail@georg.so

Rationale

The overall objective is to include useful and convenient stuff. Of course, the files are for a diverse range of applications, however, a few general themes can be derived:

• Configure Vi-like key bindings as much as possible
• Enable history where necessary (e.g. ~/.cache/program_history)
• Enable colors and completion where it makes sense

The config files don't contain personal information like hardcoded user names, email addresses, though.

Where it is supported and makes sense, the config file thus (optionally) source a local addendum. For example, .gitconfig includes .gitconfig.local at the end where a user can add truly user specific configuration like the username and email address that should be used by the program.

Usage

Clone the repository and install some symlinks in the $HOME. The repository contains a shell script that automatically creates all links.

Example:

$ cd
$ git clone https://github.com/gsauthof/user-config.git config
$ cd config
$ git submodule update --init
$ dry=1 ./install.sh

And if everything looks plausible:

$ ./install.sh

After the script is finished the $HOME directory will include some symlinks like the following:

.gitconfig      -> config/.gitconfig
.gnupg/gpg.conf -> ../config/.gnupg/gpg.conf
...

Work Tree

With a dotfiles repository, using an external work tree may look like an alternative to creating symbolic links. But this repository includes several submodules and Git doesn't support submodules in a repository with an external work tree:

fatal: /usr/libexec/git-core/git-submodule cannot be used without a working tree.