Skip to content

Latest commit

 

History

History
50 lines (31 loc) · 2.06 KB

README.md

File metadata and controls

50 lines (31 loc) · 2.06 KB

Rikkokiri's dotfiles

My quite basic dotfile setup that will hopefully evolve.

I keep my dotfiles under ~projects/ and that is what some of the scripts assume. I will update them later to use variables to make the set up more configurable.

To do

  • Adapt for zsh (currently specified for bash)
  • In script: Create 'User' file under VS Code directory (if it doesn't exist)
  • Transfer AText configuration
  • Set up pyenv

Mac settings:

  • Show Airdrop status in menu bar
  • Modify what is shown in the dock

Installation

Note: The bootstrap.exclude.sh script creates symlinks from the dotfiles in this directory to the HOME directory. Make sure that your dotfiles are backed up somewhere safe.

Open a terminal and follow along!

  1. Clone this repository: git clone https://github.com/rikkokiri/dotfiles
  2. CD into the folder: cd dotfiles
  3. Execute the bootstrap script: sh ./bootstrap.exclude.sh
  4. Restart your terminal or run source .bash_profile

Precommit hook for saving VS Code extensions

Inspired by @anhari, I've added a pre-commit hook that saves list of VS Code extensions to vscode/vscode_extensions. Set the .hooks directory from the repo to serve as git hooks directory by running

git config --local core.hooksPath .githooks/

on your machine ( source ). Or you can copy the hook to hooks directory by running

cp ~/projects/dotfiles/.githooks/pre-commit ~/projects/dotfiles/.git/hooks/pre-commit

Regardless of the method, remember to make it executable by running either

chmod +x ~/projects/dotfiles/.githooks/pre-commit

or

chmod +x ~/projects/dotfiles/.git/hooks/pre-commit

Acknowledgements

  • @ajmalsiddiqui whose articles on dotfiles and dotfile repo served as starting point and inspiration for finally getting my dotfiles repo started
  • @mathiasbynens - Dotfiles I can only dream of