DEV Community

Neovim LSP to replace VSCode

Cason Adams on December 26, 2021

If you are looking for a much simpler solution to replacing VSCode with a terminal editor I suggest reading my minimal vim post. TLDR; ...

Read full post

Sérgio Araújo • Dec 27 '21

It would be great adding a safe call at each plugin setting like this:

local cmp_status_ok, cmp = pcall(require, "cmp")
if not cmp_status_ok then
    return
end

Just in case the call fail, we just get a return without trying to read the rest of config file, the same for the packer config:

-- Use a protected call so we don't error out on first use
local status_ok, packer = pcall(require, "packer")
if not status_ok then
    return
end

Sérgio Araújo • Dec 28 '21

By the way pcall it is, if I am not wrong, the same as a try catch statement.

Cason Adams • Dec 29 '21

Great suggestion. I updated the git repo. Not sure if I should update this post or not. I am thinking no. And hopefully most people just go look at the source repo.

Kshitij Chawla • Dec 29 '21

I always add an update to my posts. A lot of new devs rely on good blogs to get started.

ChaniD • Dec 28 '21

Why?

Cason Adams • Dec 28 '21

Why replace vscode?

I work in a terminal.

Sumanth Lingappa • Jan 3 '22

@casonadams
Great article.

However, I find it difficult to understand, vscode has Remote-SSH extension and you can connect vscode to your server.

My personal experience has been 'its difficult to maintain huge nvim/vim configs over a period of time'. And instead of focusing on my actual work, I end up in configure-reconfigure vim/nvim configs most of the time.

Since I am very comfortable with vim, I use vscode-vim all the time.

Cason Adams • Jan 3 '22

Thanks! It's not that vscode is bad and yes there are some other amazing features like the remote connect offering, and live share.

For me I use nvim as my daily driver because I work in a terminal all day. And I find it fun to tweak things here and there as needed.

I do follow your word of caution that one can go down a hole of wasted time with config tweaking. And the whole point of learning vim, is that's it's installed on more servers. So if you need to hop on a machine and check it out you can. But that defeats the purpose of this article, because once you configure vim this way, it's not vanilla any more.

Thanks for your comment.

Sumanth Lingappa • Jan 3 '22

Agreed.

I am a big fan of vim/nvim and I am using vim for 10 years.

Recently, when I looked back, I was (wasting) a lot of my time in trying out new configs just for the fun of it.

And decided to stick to vscode as the main editor, ofcourse with vscode-vim extension :-)

Cason Adams • Jan 3 '22

So I tinkered with vscode for a bit, and there is just as much config with it as there is vim. With less flexibility. Going to stick with vim. Thanks for the thoughts though.

Sumanth Lingappa • Jan 4 '22

@casonadams I would love to see your work in your vim config.

Have you made any videos?

Abdoulaye Balde • Dec 28 '21

I also have a very simple and nice configuration check it out here.
github.com/abdoulayegk/dotefiles
Here is how it looks.
To install it just follow the instructions given in the above link or just download it and put the init.vim file inside the is file ~/.config/nvim then open nvim it will install everything for you.
Enjoy 😊🤩

Cason Adams • Dec 28 '21

Looks like you are using coc and viml. I have a similar (much simpler) example in this post

This post is very specific to getting up and running with neovim and the built-in LSP. Including some nice to haves to walk away from VSCode, and live in a terminal editor.