Dotfiles

🏠 Personal dotfiles for *NIX (macOS and Linux) systems.

Installation

👉 One-liner (if you trust me):

curl -fsSL https://dotfiles.wook.kr/etc/install | bash

$ git clone --recursive https://github.com/wookayin/dotfiles.git ~/.dotfiles
$ cd ~/.dotfiles && python install.py

The installation script will clone the repository into ~/.dotfiles and create symbolic links (e.g., ~/.vimrc) for you. If target files already exist (e.g. ~/.vim, ~/.vimrc), you will need to manually resolve the conflict (delete the old one or just ignore). See Troubleshooting below for details.

$ dotfiles

To update dotfiles (pull changes from upstream and run install.py again):

$ dotfiles update
$ dotfiles update --fast          # fast update mode: skip updating {vim,zsh} plugins

On Linux, you can install some common softwares locally (into $HOME/.local/bin) without sudo:

$ dotfiles install neovim         # -> ~/.local/bin/nvim
$ dotfiles install ripgrep        # -> ~/.local/bin/rg

🆘 Troubleshooting

Please read carefully warning messages during installation !!

• If something goes wrong, please run $ dotfiles update (or install.py) to make everything up-to-date.

  • If you have your own ~/.zshrc, ~/.vimrc, ~/.vim, etc., that are NOT symbolic links, they will not be overwritten by default. In such cases you should delete these files manually.

• Q: I see some weird icons like ⍰ in (neo)vim or in the statusline.

  • A: Use Nerd fonts v3. If you haven't upgrade to Nerd fonts v3 or higher, upgrade to v3 due to the new (breaking) Material Design Icons codepoints.
  • Mac users can do: brew install font-*-nerd-font. If you want to upgrade from v2, try brew reinstall --cask $(brew list | grep nerd-font).

• If neovim + treesitter emits an error like query: invalid node type, Run :TSUpdate (and wait for installation is done).

  • See nvim-treesitter#3092 for more details.

• If neovim cannot run due to version 'GLIBC_2.29' not found errors (on Ubuntu 18.04 or earlier), you should upgrade your Ubuntu distribution to 20.04+ in order to run nvim 0.8.x or higher. If you need a workaround, you can install nvim 0.7.2: NEOVIM_VERSION=0.7.2 dotfiles install neovim.

• If neovim emits any startup errors (e.g. no module named neovim):

  • Use latest neovim (e.g., neovim 0.9.0). To install/upgrade neovim on your system, you can run dotfiles install neovim (linux) or brew install neovim (mac).
  • Try :checkhealth.
  • Try :Lazy update: some errors from vim plugin could be easily solved by updating plugins to date. You can do :Lazy update (in vim) or $ dotfiles update (in zsh).
  • We require python3 version not less than 3.6. See https://endoflife.date/python
  • Make sure that the pynvim pypi package is installed on local python 3, i.e. the python3 on conda, virtualenv, etc. This should have been automatically installed. If it doesn't work, check which python3. Use the following vim command to tell which host python is used: :echo g:python3_host_prog.
    • If you are not sure, manually running python3 -m pip install --user pynvim might help.

• Does vim color look weird (e.g. only black-and-white)?

  • Check whether your terminal emulator supports 24-bit color. Use iTerm2 or kitty rather than built-in Terminal.
  • Latest Mosh (1.4.0+) support 24-bit colors yet, so try upgrading mosh if you are using it.
  • Try :set notermguicolors to temporarily disable 24-bit colors.

• Does tmux look weird? Make sure that tmux version is 2.3 or higher.

  • Run $ dotfiles install tmux to install tmux into $HOME/.local/bin, if you do not have sudo.

• If you still have no idea or have found a bug, please feel free to contact me or raise an issue, and I will happy to help you.

License

The MIT License (MIT)

Copyright (c) 2012-2022 Jongwook Choi (@wookayin)