klappradla / dotfiles

🏗 how I set up my system

dotfiles 🏗

How I set up my dev system.

About

My dotfiles follow holman's concept of "topical" organization. Each topic has its own directory with special filename conventions ⚡️:

• bin/: contains executables added to $PATH
• topic/install: script executed when installing/updating the topic
• topic/link: script executed when symlinking the topic
• topic/name.symlink: files picked up by the link script of the topic

(Note: the homebrew topic is always evaluated first as other topics depend on it.)

Installation

(on new computer: set up ssh keys first)

# start in the home directory
cd

# clone repository
git clone --recursive [email protected]:klappradla/dotfiles.git

# navigate into the new directory
cd dotfiles

# run the install script
script/setup

To install topics individually:

script/install <topic>

Tips & Tricks

• Change/disable macOS' default keyboard shortcuts for "Input Sources" if you want to use CTRL + Space as prefix in Tmux.

See docs for additional help.

dotfiles's Issues

Simplify colorscheme

Generate colorscheme (e.g. for Terminal.app) via base16 and setup Neovim to use the terminal colors only (with custom colorscheme or via https://github.com/noahfrederick/vim-noctu or https://github.com/jeffkreeftmeijer/vim-dim).

Add global editorconfig

Take a look at 898ef80#r35883824 for replacing some vim config with an editorconfig.

Get rid of vim and nvim undo files

Find a better way to handle the undo files for vim (and neovim).

Modernize Vim completion and linting

The ale and deoplete.vim setup is growing out of date and (especially the latter) causing massive startup-delays (spinning up own language servers, etc.). So maybe it's time to move over to something more modern - as in Lua based - and use Neovim's built in LSP 🤔

Some ideas:

• neovim/nvim-lspconfig has a lot of info about LSP setup (especially in the wiki)
• nvim-cmp seems a good completion solution to start with
• null-ls could replace ale for linters and even include formatters and code actions (e.g. for eslint)
• optional trouble.nvim for displaying diagnostics info
• optional mason.nvim for managing LSP and linter packages (probably overkill)

Better rsync options

Come up with better (more thought through and better documented) options for rsync (and logging).

The current options are:

rsync -atvz --delete --exclude-from \
      $EXCLUDE_LIST \
      -e "ssh -T -c [email protected] -o compression=no -x"\
      "$dir" max@"$NAS":"$BACKUP_VOLUME"

Maybe the a flag already does everything I need 🤷‍♂️

-a, --archive
      This  is equivalent to -rlptgoD. It is a quick way of saying you want recursion
      and want to preserve almost everything (with -H being a notable omission).  The
      only  exception  to the above equivalence is when --files-from is specified, in
      which case -r is not implied.

      Note that -a does not preserve hardlinks, because finding multiply-linked files
      is  expensive.   You  must  separately specify -H.  Note also that for backward
      compatibility, -a currently does not imply the --fileflags option.

(rsync man page)

Reconsider Mason

Reconsider https://github.com/williamboman/mason.nvim for managing LSPs.

Use force with lease

Find a way to adapt

git push --force-with-lease

instead of the destructive

git push --force