This repo is obtained from https://github.com/wookayin/dotfiles.git for personal use. 🏠 Personal dotfiles for *NIX (Mac OS X and Linux) systems.

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

An alternative:

git clone --recursive https://github.com/wookayin/dotfiles.git ~/.dotfiles
cd ~/.dotfiles && python install.py
=======
curl -fsSL https://dotfiles.wook.kr/etc/install | bash

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

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.

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

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

  • Read carefully warning messages during installation !!
  • 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.

• If you are using neovim and seeing any startup errors (e.g. no module named neovim):

  • Try :checkhealth.
  • Use neovim >= 0.4.2. To install/upgrade neovim on your system, try dotfiles install neovim.
  • We require python3 version not less than 3.4. Python 3.6+ is recommended (semshi: 3.5+)
  • 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.

• Powerline symbols are not displayed properly? Install Powerline fonts or Nerd fonts.

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

  • Check whether your terminal emulator supports 24-bit color. Use iTerm2 rather than built-in Terminal.
  • Try :set notermguicolors to 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.

• Ruby version is shown unwantedly? A simple workaround might be to install rvm.

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

• Powerline characters are not displayed properly? Install Powerline fonts.
• Does vim color look weird (e.g. black-and-white)? Check your terminal emulator supports 24-bit color.
• Does tmux look weird? Make sure that tmux version is 2.3 or higher.
  • If you don't have sudo, you can install it locally by $ dotfiles install tmux.
• Ruby version is shown unwantedly? A simple workaround might be to install rvm.
• After installing pylint, pytorch ops are better off whitelisted. Add below to .pylintrc.

[TYPECHECK]

# List of members which are set dynamically and missed by Pylint inference
# system, and so shouldn't trigger E1101 when accessed.
generated-members=numpy.*, torch.*

The MIT License (MIT)

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