# Installing vim with Go support

**URL:** <https://discuss.dgraph.io/t/installing-vim-with-go-support/279>\
**Category:** Users\
**Created:** [May 27, 2016, 1:39am UTC](https://discuss.dgraph.io/t/installing-vim-with-go-support/279 "2016-05-27T01:39:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [May 27, 2016, 1:39am UTC](https://discuss.dgraph.io/t/installing-vim-with-go-support/279/1 "2016-05-27T01:39:10Z")

</div>

These are the steps:

- Move your existing .vimrc, and .vim to someplace. I do these: `mv .vimrc .vimrc.backup`, `mv .vim .vim.backup`
- Ensure you have `vim-nox` installed. `sudo apt-get update`, `sudo apt-get install vim-nox`.
- Install Vundle: `git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim`
- Copy .vimrc from here: `https://raw.githubusercontent.com/manishrjain/vim/master/.vimrc`
- Run `vim`. Call `:PluginInstall`
- Run `vim`. Call `:GoUpdateBinaries`
- Download zip from `https://github.com/Shougo/neocomplete.vim`
- Ensure you have lua support. Run `vim`. Call `:echo has("lua")`. If it returns 1, you’re set.
- `unzip ~/Downloads/neocomplete.vim`, then `mv neocomplete.vim-master/* ~/.vim/`
- When you now type into vim, you should be able to see autocomplete.

Also, notice all the amazing build, test, doc browser functionality now. You can use it with `;b`, `;t`, `;g` etc. Look carefully at the `~/.vimrc` for more.

---

<div class="post-metadata">

**Author:** ![hackintoshrao](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/hackintoshrao/32/1564_2.png) [@hackintoshrao](https://discuss.dgraph.io/u/hackintoshrao)\
**Post date:** [May 27, 2016, 5:10am UTC](https://discuss.dgraph.io/t/installing-vim-with-go-support/279/2 "2016-05-27T05:10:55Z")

</div>

I had written a[blog](https://medium.com/@hackintoshrao/setting-up-vim-for-golang-programming-beginner-cheat-sheat-44181be99b9b#.sn9pipf8i) on the same a while back, might be useful.

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [May 28, 2016, 2:22pm UTC](https://discuss.dgraph.io/t/installing-vim-with-go-support/279/3 "2016-05-28T14:22:52Z")

</div>

I’ve now also checked in my new and shiny i3 window manager config, and renamed the repo:  
[https://github.com/manishrjain/dotfiles](https://github.com/manishrjain/dotfiles)

So, the links above might not exactly work. But, the `.vimrc` is here.

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [May 29, 2016, 10:19am UTC](https://discuss.dgraph.io/t/installing-vim-with-go-support/279/4 "2016-05-29T10:19:35Z")

</div>

Interesting video on how to get better at vim:

[![](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/6/680644c1454165fa8b4e1af8113a0eb6de5dfda9.jpeg "Improving Vim Speed") ](https://www.youtube.com/watch?v=OnUiHLYZgaA)

Vimgolf looks like an interesting site, but they don’t want to show you their best answers unless you provide them with a solution of your own.  
[http://vimgolf.com/challenges/55b18bbea9c2c30d04000001](http://vimgolf.com/challenges/55b18bbea9c2c30d04000001)

Also, breaking bad habits, which I have plenty of:  
[http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/](http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/)

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [November 28, 2017, 1:00am UTC](https://discuss.dgraph.io/t/installing-vim-with-go-support/279/5 "2017-11-28T01:00:32Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.