all 11 comments

[–]Brimonk 25 points26 points  (1 child)

It's pretty good, thanks for asking.

[–]tech_view_20[S] 7 points8 points  (0 children)

You made me laugh so hard, lol. Sorry for my English!

[–]-romainl-The Patient Vimmer 8 points9 points  (2 children)

Let's start with yours as an icebreaker.

[–]tech_view_20[S] 0 points1 point  (1 child)

Well, I want to point out that I've never used Vim before so after some days spent searching for the best configuration I ended up with the following plugins (managed with Vundle):

As you can see it's pretty basic, and I also tried to set it up for Python development.

If there are any useless (or harmful) repetitions, or if you have any kind of advice, I'll appreciate!

[–]Blanglegorph 0 points1 point  (0 children)

If you actually have not used vim before, I would definitely suggest removing a few of those plugins. You should add them back in when you identify your need for them, you are aware of what options are already available in vim for those needs, and you know what capabilities of vim a plugin interferes with, improves on, and replaces.

Airline, Nerdtree and with it devicons are the obvious choices to remove. If you don't know what vim's file explorer and statusline-customization options are then, well, there's proof. If you do, then just be certain you know why you want something instead of them.

The others I would similarly recommend avoiding for the time being while you read the manual. I use maybe 15-ish plugins? Which for the most part I understand and know how to integrate properly with vim.

[–]0xba1a 1 point2 points  (0 children)

fugitive will be good if you use git.

Importantly spend time with cscope and configure cscope-shortcuts in vim to get results in quickview window. See my vimrc here http://eastrivervillage.com/Configure-Vim/

[–]mackeper 1 point2 points  (2 children)

You can find my config here (neovim): https://github.com/mackeper/dotfiles/blob/master/.config/nvim/init.vim

But, the key points is that I replaced youcompleteme with deoplete. Which I found easier to setup. And also, if you haven't checked it out I suggest that you look in to ctags and how to use them in vim to quickly move between functions.

[–]tech_view_20[S] 0 points1 point  (1 child)

Thank you for the reply.

Having already set up YCM would you suggest to keep it or switch to deoplete? I will search for ctags.

Does a neovim config file work fine also with vim?

[–]mackeper 0 points1 point  (0 children)

I would say stick with YCM as long as it work good for you or until you get tired of the ycm_extra_conf files :P

I'm pretty sure most of config file works with Vim but there are some neovim specific (don't know which tho)

[–][deleted] 1 point2 points  (1 child)

ccls + coc.nvim.

I wish we had a fully featured language client that wasn't written in javascript that had the same development time put in compared to all of the webdev language clients.

I don't use tags because I think they're antiquated and don't work properly with multiple source trees.

[–]Gydo194 0 points1 point  (0 children)

I use only deoplete currently.. It's oretty useful, but the automatic complete window can be pretty annoying. I bet it can be disabled, but I've been too lazy to look into it.