Or how to alienate yourself in the world of VS Code

In my previous exploits around the terminal-based workflow -which, you can read about more here, I had setup a workflow with tmux, alacritty, and vim to great success for my average day tasks. Over the past while, I’ve wondered how I could further improve the setup and remove the context-switch which often occurred when working with other tooling such as VS Code. Plus, I may have been watching far too many of videos of the awesome (ThePrimeagen)[https://www.youtube.com/channel/UC8ENHE5xdFSwx71u3fDH5Xw] and become star-struck at the idea of digging deeper into the VIM world. So, I thought why not?

Part of this could also derive from my lack of appreciation for the IDE-like features which come bundled by VS Code by default, resulting in the features becoming more of a bloat vs convience in my usecase. My everyday tasks often involve text editing more than writing brand new modules, so the natural step in the experiment made sense. Let’s go all in on the vim world and try the long-rumored LSP integration which would restore the key feature which I leverage the most in VSCode!Let’s get started!

Installing Neovim 0.5

UPDATE: Neovim 0.5 has been officially released and can be installed via brew install neovim or through any Linux package manager

For this experiment, I had opted to use my Macbook(s) so that I could replicate the configuration and workflow for both personal and work environments. Surely if this is successful I will update my dotfiles repo and update my Fedora 33 setup accordingly! I thought that it would be a slew of build commands to get Neovim 0.5 (nightly), but luckily Homebrew rose to the challenge and provided a far easier command to set it all up: brew install --HEAD neovim.

From there, it was a matter of setting an alias for nvim to be vim purely so I can lazily save a keystroke and not break muscle memory. In the FISH shell, this can be done with alias vim nvim. No scripts breaking on me tonight!

Setting up LSP

To leverage the LSP(s), we must first install an appropriate LSP per language we want to interact with. For this test, I opted for Golang, Rust, Python and Ruby; all languages I interact with frequently in a given week. Let’s explore what’s needed to get these setup on MacOS 11, Big Sur.


I found installing on MacOS the golps server to be far difficult compared to the other language servers, which is rather intriguing because VS Code makes it look so simple with go get golang.org/x/tools/gopls@latest. On Fedora 33, running this command seemed to install the server without any issues so, shrug.


For some reason, I kept getting errors when using the rustup toolbox (which is recommended by Rust itself) and ended up installing the rust_analyzer with brew install rust_analyzer which, appeared to be a wrapper around the original rustup setup. Once installed and configured in my init.vim file, I was welcomed with this awesome completion and suggestion dialog when working in a rust project!

Completion Suggestions

Completion Suggestions Image

Function Arguments

Function Arguments Image


From a little research, Python appears to have quite a few Language Server implementations, I opted for for Microsoft’s pyright, which can be installed with npm install -g pyright. Again, once configured in my init.vim -which, I really should split into multiple files, opening any Python file would trigger the language server to initialize, and within a second or two I’d have full access to the same power found inside VS Code.


Errors Analysis Image


Solargraph has been the defacto Ruby-based LSP for the past while, and after much endorsement from my team at work, I opted to install and leverage it with gem install --user-install solargraph. From there, opening any ruby file provides me with the all-judging eyes of those who know how to write good Ruby code, and I’m reminded at-least a dozen times how much better I can improve my understanding of the language.


Code Analysis

Final LSP Configuration

  local nvim_lsp = require('lspconfig')

  local on_attach = function(client, bufnr)

    local function buf_set_keymap(...) vim.api.nvim_buf_set_keymap(bufnr, ...) end
    local function buf_set_option(...) vim.api.nvim_buf_set_option(bufnr, ...) end

    buf_set_option('omnifunc', 'v:lua.vim.lsp.omnifunc')

    -- Mappings
    local opts = { noremap=true, silent=true }
    buf_set_keymap('n', 'gD', '<Cmd>lua vim.lsp.buf.declaration()<CR>', opts)
    buf_set_keymap('n', 'gd', '<Cmd>lua vim.lsp.buf.definition()<CR>', opts)
    buf_set_keymap('n', 'K', '<Cmd>lua vim.lsp.buf.hover()<CR>', opts)
    buf_set_keymap('n', 'gi', '<cmd>lua vim.lsp.buf.implementation()<CR>', opts)
    buf_set_keymap('n', '<C-k>', '<cmd>lua vim.lsp.buf.signature_help()<CR>', opts)
    buf_set_keymap('n', '<space>wa', '<cmd>lua vim.lsp.buf.add_workspace_folder()<CR>', opts)
    buf_set_keymap('n', '<space>wr', '<cmd>lua vim.lsp.buf.remove_workspace_folder()<CR>', opts)
    buf_set_keymap('n', '<space>wl', '<cmd>lua print(vim.inspect(vim.lsp.buf.list_workspace_folders()))<CR>', opts)
    buf_set_keymap('n', '<space>D', '<cmd>lua vim.lsp.buf.type_definition()<CR>', opts)
    buf_set_keymap('n', '<space>rn', '<cmd>lua vim.lsp.buf.rename()<CR>', opts)
    buf_set_keymap('n', 'gr', '<cmd>lua vim.lsp.buf.references()<CR>', opts)
    buf_set_keymap('n', '<space>e', '<cmd>lua vim.lsp.diagnostic.show_line_diagnostics()<CR>', opts)
    buf_set_keymap('n', '[d', '<cmd>lua vim.lsp.diagnostic.goto_prev()<CR>', opts)
    buf_set_keymap('n', ']d', '<cmd>lua vim.lsp.diagnostic.goto_next()<CR>', opts)
    buf_set_keymap('n', '<space>q', '<cmd>lua vim.lsp.diagnostic.set_loclist()<CR>', opts)

    -- Set some keybinds conditional on server capabilities
    if client.resolved_capabilities.document_formatting then
        buf_set_keymap("n", "<space>f", "<cmd>lua vim.lsp.buf.formatting()<CR>", opts)
    elseif client.resolved_capabilities.document_range_formatting then
        buf_set_keymap("n", "<space>f", "<cmd>lua vim.lsp.buf.formatting()<CR>", opts)

  local servers = {'pyright', 'gopls', 'rust_analyzer', 'solargraph'}
  for _, lsp in ipairs(servers) do
    nvim_lsp[lsp].setup {
      on_attach = on_attach,

  require'nvim-treesitter.configs'.setup {
    highlight = {
        enable = true

Initial Experience A Week In

So, this blog post got sidetracked by at least a week due to other obligations coming up. Normally I’d be rather annoyed, but this provided me the chance to test the workflow out more and document my thoughts a week into using it for various use-cases.

Leveraging of the Language Servers

So, let’s talk performance. Though I need to conduct more A/B tests, I found neovim itself opens insanely quickly and the languages servers and the appropriate client connect a few seconds (less than 15 maybe?) after that. I need to compare with VS Code because I imagine this performance does not relate at all to the IDE and instead the servers themselves. The Ruby LSP for example (solargraph) takes a few seconds after the file has been loaded, and then I’m reminded once more of my failure to understand Ruby idioms at the time. I found the Rust server equally to be slower to start up in comparison, so I don’t believe the difference between an interpreted and compiled language matters in the case of the servers. Not to show my bias, but it appears we are on the same playing field in this case.

The overall coding experience of course I cannot complain about, on both iTerm and Alacritty scrolling in neovim using the mouse wheel feels fluid as it can be on a 60hz monitor. Editing code is an item I’m familiar with given my use of VI-based editors since the start of my career, but I am curious how the experience will change as I dig deeper into the workflow and also write new modules or packages using neovim exclusively. To conclude on this small section, I will remind you kind reader that I am one of those odd individuals who uses a 60% keyboard and thus, may be more attracted to chasing the non-standard purely for the novelty of it vs the value it provides. It’s a fun experiment, but equally detracts from an already established development tool which (rightly so) has become the market standard.

Bonus Feature, Telescope!

Upon digging deeper into the Dotfiles of VIM warriors, I noticed a common plugin which was deemed vital enough (spoiler, I completely agree with how amazing it is upon using it) to have dedicated YouTube video’s such as to explain it. The neovim plugin Telescope is described as,

telescope.nvim is a highly extendable fuzzy finder over lists. Built on the latest awesome features from neovim core. Telescope is centered around modularity, allowing for easy customization.

In a single phrase, I’d say that the plugin is blazingly fast and intuitive once setup for your preferred shortcuts. Essentially, it’s a glorified wrapper around common BASH commands (to overstate it from a high level), and powered via grep. Already I’ve made great use of it while working in bigger projects and the idea of fuzzy search blows my mind. Why I didn’t ever look into it before I’ll never understand, but that could be considered a mistake easily. Within a few days, I default to opening a VIM instance in the root directory of a project and navigating between files entirely using Telescope’s fuzzy search. Not to shill too much, but I can also confirm that it feels faster than leveraging a mouse to navigate directories and trees.


With the migration to Neovim, a few keybindings that I identified as essential are the following. Based on online popularity, I opted to make the leader key for when the keybinding required one.

Jump to definitiongd- Ensure your cursor is over the exact field
Format markdown table<leader><Bslash>- You need to visually select the table you want to format.
Fuzzy file search<leader>ff- Will only search for files in current Project and it’s respective sub directories.
Open VIM buffers<leader>fb- Damn useful if you have multiple files open
Toggle Line Diagnostics<leader>e- This will shut the servers up and let me write bad code!