dotkyl

my dotfiles (my initials are kyl)

Contents

/bin

Half of these are from other people's gists or other uninstallable utils. The other half are dumb things I wrote.

/bookmarks

Empty directory (in git) which will contain symlinks to bookmarked directories.

/completion

Zsh completion scripts that I couldn't get from homebrew zsh-completions. Not many.

/home

Actual dot files, without the dot. bin/setup-dotfiles symlinks them to home dir (with the dot).

/iterm

iTerm2 themes.

/lib

Files that are sourced by ~/.zshrc. Coolest thing in here is bookmark.

/nvim

Neovim configuration -- init.vim plus some custom syntax and colors. Also vim-plug.

bin/setup-dotfiles symlinks this directory to ~/.config/nvim.

If you looked at my init.vim, yeah I know, I have too many plugins. Half of them I don't even use. I'm a plugin hoarder. We could make a TV show about people like me.

crontab.txt

I always set my crontab with crontab crontab.txt instead of directly with crontab -e so I can keep it under version control. One less thing to re-figure out on clean install. Unrelated.

Install

These installation instructions are for my future self. But I guess they could be useful if you decided to set up your dotfiles like mine.

cd ~  # this is important or setup-dotfiles won't work
git clone git@github.com:katylava/dotkyl.git .dotkyl
.dotkyl/bin/setup-dotfiles
cp path/to/000-private.zsh .dotkyl/lib/

Neovim

To set up neovim with python support, install both major versions of python via homebrew first, then use each version's pip to install python stuff for neovim. I don't know the perfect setup for neovim+python, but this works for me, I think because of these two lines in my init.vim. There are probably disadvantages to this method when working in a virtualenv.

brew install python python3 neovim/neovim/neovim
pip install neovim
pip3 install neovim

To finish setting up neovim, open it and do :PlugInstall.

Usage

Some people keep dotfile repos so they can clone them to servers they work with and have the same settings everywhere. That's not why mine are here. They are here for sharing and for re-installing after a clean install of Mac OS. I would not set these up on a server.

TODO

• Add a way to sync relevant ~/.config files and directories (besides nvim)
• Add alternate zshrc for use inside nvim terminals.
• Find a way to keep secrets even secreter via keychain. This looks useful.
• Terminal palettes – find some way to store and use themes with alternate colors which go with the main 8 terminal colors.
• Write my own prompt code, maybe in Rust (current prompt was generated by promptline.vim and then modified).