Im also not getting Clojure when calling :nmap,
n <NL> * /<+.\{-1,}+><CR>c/+>/e<CR>
n \gp * :GitPullRebase<CR>
n \gc * :GitCommit<CR>
n \gA * :GitAdd <cfile><CR>
n \ga * :GitAdd<CR>
n \gl * :GitLog<CR>
n \gs * :GitStatus<CR>
n \gD * :GitDiff --cached<CR>
n \gd * :GitDiff<CR>
n \C :call CapitalizeCenterAndMoveDown()<CR>
bp <Esc>:bp<CR>
bn <Esc>:bn<CR>
n gx <Plug>NetrwBrowseX
st a)<Esc>^i(<Esc>$:w<CR>
n <Plug>NetrwBrowseX * :call netrw#NetrwBrowseX(expand("<cWORD>"),0)
<CR>
<M-Up> gk
<M-Down> gj
Which exact version of contrib should be used?
On Sep 4, 12:01 am, Bokeh Sensei <bokeh.sen...@gmail.com> wrote:
> Hi Meikel,
>
> I think you did a fantastic job with VimClojure!
> It's really what has gotten me started with Clojure and back to Java.
>
> I had very carefully read your instructions, including the README.txt,
> but still managed to not get it to work at first.
> Of course I was the one that screwed up! Problem is, I had no idea
> where it was that I screwed up!
> Really, the question is, what should we assume the user should know/
> doesn't know/shouldn't know.
> For instance, there might be some implementations details that may be
> important when installing, but likely to change
> as VimClojure matures.
>
> So, instead of adding more to the documentation, which could further
> confuse the user, maybe we could try this:
> - gather all the necessary installation steps, in the right order
> (done! in your head at least)
> - ask someone to write a single test for each step, and bunch 'em up
> in a bash script
> - notify the user when that step has failed.
>
> For instance, a typical question I had, but could not verify, is : is
> my classpath correct? Oh, yeah, that tilde thing...
> An experienced Java user might laugh at this, but a beginner, or a
> casual user would think differently.
>
> We understand how much energy you put into this, so instead of having
> you write tests, maybe someone else could do it.
> I would love to, for the little stuff I know.
>
> Another, perhaps stupid sounding point :) I want to make, is I think a
> Vim+VimClojure+NailGun+Clojure self-contained box would work great.
> All three would be so small a footprint (1/10th of Netbeans...), I
> don't care for the redundancy of installs if I can install them and
> get going in a few clicks.
>
> Again, thank you for all your efforts and also the time you spend
> answering people on the forum!
>
> Vielen Danken!
>
> Bokeh
>
> On Sep 2, 11:14 pm, Meikel Brandmeyer <m...@kotka.de> wrote:
>
> > Hi,
>
> > On Sep 3, 2:21 am, Bokeh Sensei <bokeh.sen...@gmail.com> wrote:
>
> > > vimclojure took me a whole weekend to get started.
> > > it's sensitive to how it's setup, but with no way to automatically
> > > verify the correctness of it.
>
> > Ok. I give up. Obviously I'm not able to explain how to install
> > VimClojure, neither with the README nor with the screencast.
>
> > ANY VC USERS OUT THERE WITH A RUNNING SETUP!
> > Please think about contributing some documentation on how
> > to setup up VimClojure! I'm routine-blinded so any documentation
> > from the "outside" with a fresh view is highly appreciated!
>
> > > Try this in vim:
>
> > > :call vimclojure#Repl.New()
>
> > Please don't do that. Poking in the guts doesn't help. The problem is
> > more likely in the setup.
>
> > On Sep 2, 10:31 pm, ronen <nark...@gmail.com> wrote:
>
> > > Iv been trying to use the Nailgun functionlity of vimclojure but Im
> > > stuck on a silly issue, Im hitting <LocalLeader>el inside:
> > > (println "hello")
>
> > > And nothing happens, same goes for the rest options.
>
> > Things to check:
> > - Did you install the vim side of the plugin? ("ant install" should
> > be sufficient)
> > - Did you enable filetype plugins and syntax highlighting?
> > - Is the filetype of the buffer correctly set to "clojure"?
> > - Are the key mappings set up correctly? (Check with "nmap" and look
> > for something like "Clojure....")
> > - Are there error messages? (Check with ":messages")
>
> > This should cover the "nothing happens" case. If that doesn't help, I
> > will need a more detailed description, what you did to setup VC and
> > how your .vimrc looks like. If there are failure messages, I'll need
> > the message content. (Not the whole stacktrace, but what the message
> > said...)
>
> > > In addition its not clear to me how to start the REPL the doc/
> > > README.txt says:
>
> > > "Start a Repl via the |sr| shortcut. At the prompt just type
> > > expressions"
>
> > > Im typing sr with and without pipes with no avail.
>
> > The pipes are a marker for Vim's online help system. Run ':helptags
> > ~/.vim/doc' after installing the Vim plugin of VC to regenerate the
> > tags file. Then hitting <C-]> on the text in the pipes or (in gvim)
> > double-clicking it will jump to the referenced documentation. There
> > you will be told that the key mapping is '<LocalLeader>sr'.
> > '<LocalLeader>' is a configurable key which defaults to \. So the
> > correct key mapping to start a repl is \sr. Similar the other
> > mappings: \et, \eb, \lw, ...
>
> > The '<LocalLeader>' can be configured via the special maplocalleader
> > variable. When you put 'let maplocalleader = ","' in your .vimrc, the
> > mappings will be ,et etc...
>
> > More on these topics:
> > :help helptags
> > :help mapleader
> > :help maplocalleader or :help <LocalLeader>
>
> > > My vimrc settings are:
> > > " Vim Clojure
> > > let vimclojure#NailgunClient = "/home/ronen/.vimclojure/ng"
> > > let clj_want_gorilla = 1
> > > let clj_paren_rainbow = 1
> > > let clj_highlight_builtins = 1
> > > let clj_highlight_contrib = 1
>
> > > Im starting Nailgun with:
>
> > > java -cp ../.clojure/:build/vimclojure.jar:src/
> > > com.martiansoftware.nailgun.NGServer 127.0.0.1
>
> > This will not be sufficient. You will also need clojure.contrib.pprint
> > and clojure.contrib.def in your classpath. Also the clojure directory
> > looks suspicious. Did you mean the clojure.jar?
>
> > Sincerely
> > Meikel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
