Problems With VimClojure (Minimal Example Included)

3 views
Skip to first unread message

Tim Sally

unread,
Oct 4, 2009, 6:14:23 PM10/4/09
to Clojure
Hey all,

I'm having a problem getting VimClojure working. I've tried with both
the development and stable versions. For this minimal example, I use
the stable version and ivy to resolve the dependencies. However I
have tried installing with a correct local.properties file as well
with no luck.

.vimrc: https://pastee.org/t828u
tarball of my .vim directory (post install): http://dl.getdropbox.com/u/223699/vim.tar.gz
ant build log: https://pastee.org/ey254
ant install log: https://pastee.org/3adj

mil:~ tim$ vim --version
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 13 2009 22:28:10)

When I open up a Clojure test file, the paren rainbow works. The
function autocomplete works as well. However :nmap lists none of the
local keybindings. :messages doesn't list anything useful.

Any help would be appreciated.

Tim

Meikel Brandmeyer

unread,
Oct 5, 2009, 4:27:51 AM10/5/09
to Clojure
Hi,
Thanks for the detailed information about you settings. Did you start
the nailgun server before opening the file?

Sincerely
Meikel

Tim Sally

unread,
Oct 5, 2009, 5:02:09 AM10/5/09
to clo...@googlegroups.com
Hi,

At the moment I'm only interested in the documentation lookup
functions, so I did not start the nailgun server. I had assumed that
the nailgun server was only necessary for evaluating code, but I
didn't read the README carefully enough. Starting the server was the
missing step.

Thanks for clearing that up!

Tim

Meikel Brandmeyer

unread,
Oct 5, 2009, 8:17:11 AM10/5/09
to Clojure
Hi,

On Oct 5, 11:02 am, Tim Sally <t...@activeattack.com> wrote:

> At the moment I'm only interested in the documentation lookup  
> functions, so I did not start the nailgun server.  I had assumed that  
> the nailgun server was only necessary for evaluating code, but I  
> didn't read the README carefully enough.  Starting the server was the  
> missing step.

The documentation lookup basically retrieves the doc metadata from the
Var in question. So it needs to have the server running. Otherwise it
would be pretty hard to have doc lookup for libraries involved: you
have to somehow generate offline documentation, put it somewhere, tell
VC where this "somewhere" is... Using the server for doc lookup Just
Works(tm). Instantly. For everything providing docstrings. Without
further configuration needed. So my decision went with the dynamic
lookup.

Sincerely
Meikel
Reply all
Reply to author
Forward
0 new messages