Robin Gagnon

Posted on Sep 18, 2020

Show and tell: Show off your vim setup 🚀

#discuss #beginners #vim #productivity

Hey DEV!

I was inspired by the post about vscode setups, so I decided to create this one.

I would love to see what the vim users of the DEV community use the most from color schemes, plugins, workflows, etc.

Starting with mine:

Check out the dotfiles. (Use as a reference only, it is not yet documented ☹️)

Color scheme

I use iceberg.vim, made by the great designer cocopon.

Check out cocopon's work!

Plugins

I don't use many plugins, but 3 are vital right now to my workflow:

fzf
- Fuzzy find a file by its name
- Search for text in all files
- Quickly switch between open vim buffers
coc.nvim
- autocompletion for many languages through extensions
vim-fugitive
- Resolve conflicts
- Stage changes line by line

Outside vim

tmux to manage terminal panes
typewritten, a minimal async zsh prompt

Share your own! 🚀

Latest comments (49)

Peter Benjamin (they/them) • Aug 25 '21 • Edited

My setup is very minimal to allow for simplicity and portability across wide range of development environments I use frequently (e.g. local machines, remote servers, raspberry pi's, docker containers) without compromising productivity.

Vim

Default colorscheme. Rely on terminal emulator for colors or just use black/white in some environments.
No plugins, but important features are implemented.
vim-unimpaired features
vim-fugitive features
Build and test results are pattern matched against :h 'errorformat' to load errors into vim's quickfix list. Also, show signs in signcolumn, like ale & sytantic plugins.
FZF repo ships with basic vim function definitions that are leveraged
vim-rooter feature

Tmux

Again, little to no plugins, but important features are implemented.
window/pane controls
status bar settings
fzf-url to launch URLs in tmux pane/window without the mouse or manual copy/paste
Custom project launcher to launch new tmux windows directly in the root of repositories.

Git

A number of custom git subcommands
For example, vim-fugitive's :Gbrowse (i.e. opening a repo, file, and line number on github/gitlab) is here: git browse <filename> <starting line> <ending line>
Remote Containers from VSCode is here: git devcontainer

Shell

Bash shell. Not a lot of customization. .bash_prompt only shows user, hostname, current working directory, git branch & status info, aws context, kubernetes context, and background jobs.
Limit dependencies on CLIs that need to be installed directly on localhost to: fzf, git, curl, docker, make. Everything else should be runnable via docker
Bash functions for kubectl and searching the web

Screenshots

Siddharth • Aug 5 '21

I've only been using vim for 2 months. I even wrote a blog post when I started, which has all sorts of vim tips in the comments

Andrew Baisden • Oct 13 '20

Interested in seeing more want to get better at using Vim.

David Cantrell • Sep 21 '20 • Edited

Wow, some of those make mine look really garish!

My config: github.com/DrHyde/configurations/t...

Robin Gagnon • Sep 22 '20

Looks old school I like it!

David Cantrell • Sep 22 '20

Yeah, I've not really fiddled with the colours much, apart from tweaking them a bit to work better in Dark Mode.

But that's not old school. Old school is green on black in a tiny dumb terminal. I don't miss that.

Robin Gagnon • Sep 22 '20

Good point!

Cason Adams • Sep 19 '20

I always keep coming back to good ole gruvbox.
I just recently switched from skim to use fzf because it is more mature.
As others I am using neovim with coc works really well with rust, python, bash
tmux is awesome to have command line and vi at the same time with gitmux
loving Alacritty for my terminal and JetBrains as the font

dotfiles

Bhupesh Varshney 👾 • Sep 19 '20

Editor : nvim
colorscheme: purify

Everything possibly documented in my dotfiles repo

Frans Allen • Sep 19 '20

currently, this theme is my favorite

my .vimrc

set ts=2 sw=2 cc=80 expandtab number noswapfile
colorscheme delek

Robin Gagnon • Sep 19 '20

Minimalism goals

Jordan Kicklighter • Sep 19 '20

Not sharing a setup, but curious from anyone around here mentioning COC: how is LSP integration in Vim? Curious about JS/TS, VueJS, Ruby, and any other languages people have tried. The tooling is one of the reasons I stick with VS Code.

Ganjar Gingin Tahyudin • Sep 19 '20

how to can debug some go/js/python/ruby projects in vim/nvim ? i just confused because of that ...

Robin Gagnon • Sep 19 '20

I will agree with Justin that vim + coc is just as good at LSP than vscode.

It uses extensions for languages so you add the ones you work with and they get loaded when a file of that language opens.

There are extensions for all the languages you listed so you should be golden.

Good luck!

Justin Ho • Sep 19 '20

I've used VS Code and I think coc is just as good at LSP for JS, React snippets and C# (only languages I've been using since switch).

In addition it's the most familiar since the eslint and prettier plugins gives you the same warnings and formatting as you would running the linter/ formatter in cmd.

The biggest hurdle is to learn how to use vim though.

Jordan Kicklighter • Sep 19 '20

I'm very comfortable with Vim, and I use the plugin in vs code. I'd go back to Vim if these plugins make the experience similar. Thanks for the feedback

Justin Ho • Sep 19 '20

Sorry I didn't mean to imply you don't know how to use vim.

I meant that I'm not even that comfortable with vim and still need to remind myself to not hold down 'j' and use the line numbers 😅

Jordan Kicklighter • Sep 19 '20

Oh no, I didn't take it that way! Just clarifying that the Vim part is what I want in my life, but the other features are keeping me in VS Code.

And don't worry, I've been using Vim for years and still catch myself holding down j. Then I catch it, move back up, and use a line number to reinforce the better habits.