- check the version of vim:
vim --version
- if <8, upgrade!
brew install vim
did the trick on macOS- ubuntu:
- had to add
add-apt-repository
ability:sudo apt-get install -y software-properties-common
sudo add-apt-repository ppa:jonathonf/vim
sudo apt-get update
sudo apt-get install vim
- had to add
- clone repo into working directory
git clone https://github.com/carylwyatt/dotfiles.git
- copy .vimrc to user directory
cp .vimrc ~/.vimrc
- install Vundle
git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim
- launch vim and run
:PluginInstall
live at ~/.config/nvim/init.vim
-- which you'll probably have to create
Neovim uses vim-plug
instead of Vundle, so install that like this:
curl -fLo ~/.local/share/nvim/site/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
then:
nvim
:PlugInstall
cp .bash_profile ~/.bash_profile
cp .git-prompt.sh ~/.git-prompt.sh
brew install git bash-completion
if ubuntu, you'll need to add this line to the bottom of ~/.bashrc
:
. ~/.bash_profile
- if you're still getting a bash error about
PS1
, try:sudo apt-get install git-core bash-completion
to double check git-completion installed properly
- follow instrcutions at dracula for iterm for setting iterm theme
- key remaps:
- change right command key to control
- change "to switch panes" to opt-number
- once you've installed powerline fonts and symbols, head to preferenes > profiles > text and change font under Font to
source code pro
and Non-ASCII Font toPowerlineSymbols
2022 UPDATE Just use nerd fonts. Easiest choice is to set iTerm2 fonts to "Hack Nerd Font Mono", 13 pt, use the ligatures. It's easy, and it's fine.
For whatever reason, great fonts and symbols are automagically included in ubuntu 18.04, so no need to install any of these powerline fonts unless you really want them! However, you'll probably want emoji support for your unicorn, so sudo apt-get install fonts-emojione
Mostly followed these instructions:
- How can I install and use powerline plugin
- Powerline fonts repo
- on macos, you still clone the repos below, but just click the + icon in fontbook and select that folder to add them to your system
wget https://github.com/Lokaltog/powerline/raw/develop/font/PowerlineSymbols.otf
wget https://github.com/Lokaltog/powerline/raw/develop/font/10-powerline-symbols.conf
sudo mv PowerlineSymbols.otf /usr/share/fonts/
sudo fc-cache -vf
sudo mv 10-powerline-symbols.conf /etc/fonts/conf.d/
- restart terminal
This took me forever to figure out, but it was as simple as cloning the powerline fonts repo and moving folders around š¤·
git clone https://github.com/powerline/fonts.git
mv fonts/SourceCodePro /usr/share/fonts/
sudo fc-cache -vf
- restart terminal
- open terminal preferences: Edit > Preferences
- on the appearance tab, use dropdown to select font
- while you have preferences open, on the advanced tab, change the default character encoding to utf-8 (unicode)
Since macOS Catalina will be changing the default shell from bash to zsh, I've started working on tricking out my zsh setup. Of course I'm using oh my zsh, so head to their homepage for install instructions. Then:
cp .zshrc ~/.zshrc
cp agnoster.zsh-theme ~/.oh-my-zsh/themes/agnoster.zsh-theme
I spent a few hours trying to figure out why my agnoster symbols didn't match their README images... turns out the agnoster file shipped with the oh my zsh install is out of date. Mine is the latest (as of June 2019).
One other change I made in iTerm is under Preferences > Profiles > Colors: change Black to 20% Gray (you can choose this options when you click on the black square under "Normal") so it's not so starkly black behind the unicorn emoji.
On macOS, I had issues with the stupid ^M
carriage returns in the zsh files and got a "parse error". See parse errors issue in the oh my zsh repo for the workaround.
Getting powerline fonts and symbols set up for oh-my-zsh was a whole thing, and I finally figured out why: I had all my font config stuff "installed" in my /home/caryl (user) files but for zsh, they needed to be installed/configured in the ~ (root) files.
Oy. All of the above is still valid, it just needs to go in two places??
Can't really believe it's working, but it is! Here's the installation I followed:
I had to create the application folder in the .local directory, but other than that, this worked! Now to figure out how to create a keyboard shortcut to launch this terminal instead of the default version.
Update (Jan 2019): Found a new way, and this legit works: add if statement to end of ~/.bashrc
if [ "$COLORTERM" == "xfce4-terminal" ] ; then
export TERM=xterm-256color
fi
DOS and UNIX files don't get along. I've had many issues in the past with the stupid LF vs CRLF line endings/carriage returns. Here's the official Github statement on it: Dealing with line endings.
I have two settings globally:
git config --global core.autocrlf input
git config --global core.safecrlf false
You can check these settings in any git-enabled directory with git config --list
.
Most recently, these stupid ^M
errors threw off my entire vim setup after I decided it was a good idea to update all my plugins. I'm basically obsessed with my vim settings, so this was not only a pain in the ass but kind of terrifying. What ended up fixing it was deleting the plugins that were causing the issue (they live in ~/.vim/bundle
, use rm -Rf [name of plugin directory]
) then re-installing the plugin via Vundle (vim +PluginInstall +qall
).
if docker is giving you the docker deamon connection error, try:
sudo service docker start # Ubuntu/Debian