I have added installation instructions. I added 2 options which I believe to be
the best, however there are other options. I'll expand on that. In the
go.tools/cmd/oracle we could add some sort of directory structure along the
lines of go.tools/cmd/oracle/vim/ftplugin/go.vim (if ftplugin is desired
behavior, which I think is correct in this instance). The user could then set
rtp+=.../go.tools/cmd/oracle/vim . I think the options I have provided are a
little cleaner on the go.tools side of things, but there is no right way to make
a PB&J. 
I left the g:loaded_oracle stuff... see kisielk comment for rationale. I would
still delete if such behavior is still unwanted. (not really meaning to be an
annoyance, I realize what a small bugaboo it is. it's just the "vim" way i've
seen in my use so far)
Also, I believe this "rudimentary" integration is at least sufficient to be of
use to Vim users at this point. Feel free to expand on the so called "usability
improvements" that are needed. I've found it pretty useful recently and don't
really have any complaints, but I'd be happy to work on said improvements.
https://codereview.appspot.com/14480043/diff/6001/cmd/oracle/oracle.vim
File cmd/oracle/oracle.vim (right):
https://codereview.appspot.com/14480043/diff/6001/cmd/oracle/oracle.vim#newco...
cmd/oracle/oracle.vim:18: " load this plugin once
On 2013年10月10日 21:11:01, kisielk wrote:
> On 2013年10月10日 19:09:58, adonovan wrote:
> > On 2013年10月08日 04:16:45, rdallman10 wrote:
> > > On 2013年10月07日 18:25:43, adonovan wrote:
> > > > What problem does this solve? (The equivalent code in Emacs would be
> > > > undesirable because it's common to load and re-load a script under
> > > development.)
> > > > 
> > > > Perhaps you want the test to say "vim -u /dev/null" to make it
independent
> > of
> > > > user configuration.
> > > 
> > > Honestly, great question. The best I can come up with is that it saves the
> > load
> > > time for vim on startup / config change. This boilerplate along with a
"set
> > > &cpo" I've seen in almost every vim plugin I've come across. VimL is
awfully
> > > slow, I guess I've just always deemed it good practice. 
> > > 
> > > I do see your point. Will remove if desired. 
> > 
> > Please do. If we don't know we need it, we shouldn't include it. If we
don't
> > even know what it does or why, we especially shouldn't include it. :)
> 
> From :helpgrep NOT LOADING:
> 
> It's possible that a user doesn't always want to load this plugin. Or the
> system administrator has dropped it in the system-wide plugin directory, but a
> user has his own plugin he wants to use. Then the user must have a chance to
> disable loading this specific plugin. This will make it possible: >
> 
> 6 if exists("g:loaded_typecorr")
> 7 finish
> 8 endif
> 9 let g:loaded_typecorr = 1
> 
> This also avoids that when the script is loaded twice it would cause error
> messages for redefining functions and cause trouble for autocommands that are
> added twice.
> 
> The name is recommended to start with "loaded_" and then the file name of the
> plugin, literally. The "g:" is prepended just to avoid mistakes when using
> the variable in a function (without "g:" it would be a variable local to the
> function).
I found this url:
http://vim.1045645.n5.nabble.com/the-plugin-startup-check-td1200734.html which
offers a similar sentiment. Will let the debate roll on until further notice,
though I amended the variable to fit the naming convention.