search

fatih / vim-go

Go development plugin for Vim
https://www.patreon.com/bhcleek
Other
16.01k stars 1.45k forks source link

Not an editor command: GoRun #419

Closed jakub-id closed 9 years ago

jakub-id commented 9 years ago

OK, I am sure I messed something up. I am using pathogen to install the plugin. I ran :GoInstallBinaries which worked OK. I see syntax highlighting is there. Yet I can't run any of the commands: :GoRun, GoDoc, etc. Ideas?

fatih commented 9 years ago

This is not vim-go related issue. Search for the issues please. You didn't installed vim-go properly. Please use pathogen or any other plugin manager to avoid problems. Thanks.

jakub-id commented 9 years ago

I am using pathogen, as I have wrote above. Also, :GoInstallBinaries did work so some parts of the plugin seem to work. This is the output of :scriptnames:

38: /Users/jakub/.vim/bundle/vim-go/syntax/go.vim 39: /Users/jakub/.vim/bundle/vim-go/indent/go.vim

Do you see anything obvious missing?

fatih commented 9 years ago

Check this out: https://github.com/fatih/vim-go/issues/282#issuecomment-69174561

jakub-id commented 9 years ago

That did the trick, thanks! Would it make sense to add to the README for future reference?

fatih commented 9 years ago

@skoczko this is not vim-go related, it's something because pathogen was not installed properly. vim-go doesn't rely on pathogen, you can use vundle, plug, vim-plug, neobundle, etc.. there is a lot of options to choose. Thanks for bringing this up though :)

BruceWangNo1 commented 5 years ago

I encountered the same problem. I looked through a lot of the related issues. No dice. I came across this page and I ran git clone https://github.com/fatih/vim-go.git ~/.vim/bundle/vim-go and :GoInstallBinaries in vim. "GoRun" is now available.

FantasyLeo commented 2 years ago

feedback

I encountered the same problem.

I used vim8, and installing by following:

I solved it by adding the following to the file .vimrc:

" Enable filetype plugins 
filetype plugin on

Would it make sense to add to the README for future reference?

Think twice. @fatih

Thanks all.