CLIfe or my development setup

Like many other people, I’ve started my programming journey by using big, powerful, clunky IDEs. I’ve used , etc. As the time passed, and I slipped more into the web development, I switched to lighter options. For a while, my editor of choice has been . About three years ago, I’ve completely migrated to , , and other non-GUI tools, and I’m totally in love with them so far! Borland Delphi, MS VS, Netbeans, Eclipse, IntelliJ IDEA Sublime Text Vim Tmux Two things triggered the migration. First, at my new job, we all had laptops for working remotely, but most of the development was happening on the powerful stationary workstation located in the office. Using or over a shaky internet connection was a pain in the butt, so I needed a better option. Second, I was doing more and more of a DevOps kind of work, which required me editing files on dozens of remote machines every day, and was the only editor available everywhere. Switching to solved both problems for me, and after I discovered , and the , I completely ditched as my primary editor. Recently I noticed that more and more people are asking about my setup whenever they see my screen, so I decided to share it in a blog post. SSHFS VNC Vi Vim the ergonomics plugin ecosystem Sublime Installing Neovim is an ambitious project of refactoring a 27 years old codebase from scratch. You can read more about their vision .Ways to install vary per OS, so it’s better to refer to the . From here on I’ll assume , but most of the configuration will be OS-independent, only installation steps will be different.In is included in the distribution, so you can just do Neovim Vim here Neovim original guide Ubuntu 18.04 Ubuntu 18.04 Neovim sudo apt-get install neovim On it is available via : Mac OS Homebrew brew install neovim To invoke , you’d need to call , which is one letter longer than just and isn’t compatible with machines where there’s only regular vim available. To fix this you can define an alias in your rc script: Neovim nvim vim alias vim=’nvim’ I personally chose a hardcore way: deleted a and replaced it with a symlink to the Neovim: /usr/bin/vim sudo rm /usr/bin/vim && sudo ln -s /usr/bin/nvim /usr/bin/vim Installing Plug Before doing anything else with , it’s better to install a plugin manager. I chose , because it’s very minimalistic and still does the job. To install for : Vim vim-plug Plug Neovim curl -fLo ~/.local/share/nvim/site/autoload/plug.vim --create-dirs \https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim is the only plugin that needs to be added manually, the rest of them will be installed . Vim-plug via Plug Installing Tmux The next thing we’ll configure is . Tmux is a terminal multiplexer, which allows us to do these key things: Tmux Split a terminal window into horizontal and vertical panels Split a single terminal into multiple windows Keep all the processes running in alive, even if we lost an connection. Tmux SSH runs on the remote side (if we’re talking about development on the remote machine) and is itself split into a , and a . When you connect to your workstation via , you first launch a , which then connects to a , running on the same machine as a daemon. When the connection drops, terminates only the part, as it was the only child started by the process. Now, on , a fresh enough is already included in the distribution, so just do: Tmux tmux-server tmux-client SSH tmux-client tmux-server SSH tmux-client SSH Ubuntu 18.04 Tmux sudo apt-get install tmux On other platforms, please make sure you’re installing , as some things in my config are incompatible with older versions. tmux >= 2.0 Installing Zsh I prefer over bash, because of few extra features it provides: a command history, shared among all running shells, fancier command autocompletion, and extensibility through . On run: Zsh oh-my-zsh Ubuntu sudo apt-get install zsh and then make it a default shell for your user: chsh -s /bin/zsh (then re-login) To add : oh-my-zsh sh -c "$(curl -fsSL )" https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh Fzf Who doesn’t love a fuzzy search? sudo apt-get install gitgit clone --depth 1 https://github.com/junegunn/fzf.git ~/.fzf~/.fzf/install Then just answer yes to everything, and it will make your ZSH fuzzy in several ways. Just try pressing Ctrl+R or Ctrl+T. ~/.zshrc customizations Here are some things I like to have in my rc file: Finally, we’ve installed all the core tools and can now move on to the configuration. Let’s first take a look at my config. Vim Tweak it to your taste, put under , open , and then run to install all the plugins (ignore startup errors when opening the ). ~/.config/nvim/init.vim Vim :PlugInstall Vim To complete the installation: YCM cd ~/.local/share/nvim/plugged/YouCompleteMesudo apt-get install build-essential python-dev cmake./install.py And then, to get rid of these weird symbols at the bottom of your : Vim sudo apt-get install fonts-powerline (you may need to restart your terminal after a font installation) After all the manipulations your should look somewhat like this: Vim Tmux config I’ve done a few tweaks to my config as well.As with , you should start by installing a : Tmux Vim plugin manager git clone ~/.tmux/plugins/tpm https://github.com/tmux-plugins/tpm Here’s my full config: Tmux Put it under (and ) and (re)start your . On the first start press to install Tmux plugins (default prefix is Ctrl+b) ~/.tmux.conf ~/.tmuxline Tmux prefix I Here’s the screenshot after completing all the steps above: You should be able to recreate my setup by just copying and pasting stuff from this post. The real beauty of CLI tools is that they’re incredibly customizable. You should definitely take this config and use it as a template for your own experiments! A few more tips at the end: Vim doesn’t make sense without navigation, so get used to those damn . Vim HJKL Try remapping to , especially on new Mac laptops CapsLock Esc Get yourself one of those curvy keyboards, and your hands will thank you! That was it for this post. If you liked it, you could also check out . what am I building using all these tools Links My engineering story Another reason why your Docker containers may be slow A Knowledge Base right in your Slack