dotfiles

My dotfiles, based on the 3 things I value the most when working on the terminal:

• Editing capabilities
• Accessibility
• Performance

These are not setup to cover everyone's needs. In fact, they relate to my current work and change every other week.

If you like what you see and plan on using it, please first take a look at the settings themselves, since you'll be using them at your own risk.

Overview

The aim is for the workspace to be simple enough that's not full of clutter but still shows everything needed at any given time.

• Terminal: Kitty + Tmux
  • Theme: Nord
  • Shell: Zsh + Zgen
  • Font: Source Code Pro for Powerline
• Editor: Nvim

Editing (todo)

Accesibility (todo)

• Better Touch Tool: When working on my macbook Pro I felt some accessibility issues which MacOS does not easily allow to configure. I use BTT to standardize how I move around the OS, so I can move on the same manner I move around the terminal and text editor.

Performance (todo)

Other (todo)

Installation

Currently using Gnu Stow to manage the files, inspired by Brandon Invergo's post.

Using stow with home as the target dir

stow -t ~/ [package-name] to install package

stow -D -t ~/ [package-name] to remove package symlinks

stow -R -t ~/ [package-name] to restow/refresh package symlinks

Non-stowable packages are suffixed with *-config.

Using brew

Create Brewfile in the current directory

brew bundle dump

Install everything from the Brewfile

brew bundle

Note: brew bundle -h for further info.

Using npm

Get all user-installed packages into a file

npm list -g --depth=0 > npm-packages

Plugging nvim

• Open nvim after stowing the package and call PlugInstall (and PlugClean first if necessary).

Todo

• Finish README
• Install scripts + Makefile
• Sublime Text config
• Improve where files are localed (symlinked into). Most of the files are sourced according to a root env var anyway, so maybe we can come up with some kind of organization.
• Document the choices for shell optimisation