Julian Prein
e8a8f9637a
CoC disables backup files due to a problem with a typescript language-server (it becoming slow when the backup file is written, triggering a `structureChanged`). But: 1. I want backup files 2. I do not use that language server 3. If I would: 1. I could disable backup files in a filetype plugin 2. The linked issue is from 2019 - no idea if this is still present today 4. I don't think this issue is even a thing with a `&backupdir` that does not include relative directories (which is the case for me) So remove the lines disabling backups and go back to vim's defaults: `nobackup` and `writebackup`. Link: https://github.com/neoclide/coc.nvim/issues/649
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 kitty 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