Julian Prein
d89fd6653c
Starting a new kitty process is quite slow. With --single-instance "new invocations will instead create a new top-level window in the existing kitty instance"[^1] to allow "kitty to share a single sprite cache on the GPU"[^1], so that startup is almost instant. For this to work best, launch one hidden "daemon" instance at startup so that the kitty process is always running, even when no OS windows exists. [^1]: kitty(1) Link: https://github.com/kovidgoyal/kitty/issues/330
My dotfiles
This is a collection of the configuration files and scripts I use for various tools and environments.
Although some files support macOS, most of them assume that they are used on a GNU/Linux system. The systems I use include an Artix, a Manjaro and an Ubuntu installation. All of them running i3wm and the arch-based systems without a DE. I use my fork of st as terminal, zsh as shell and neovim as text editor.
The repository mimics my $HOME, trying to conform to the XDG Base Directory
Specification as close as possible. An exception is etc/ -> /etc/, as well
as meta/ and some other files in the root of the repository (e.g. this README
or the LICENSE) which are not in my $HOME.
The most interesting files are probably in .config/zsh, .config/vim and .config/tmux.
Installation
The repository content can be installed via dotbot. All existing files which would be overwritten are first packed into an archive for backup (see meta/archive) and then dotbot places symlinks in the appropriate places for the different files and folders in this repository.
To start the installation run:
$ ./meta/install