Hello, I have figwheel server running with ‘lein fighweel’ and auto-reloading on filechanges works fine. But I can not use the REPL from VIM: org.mozilla.javascript.EcmaError: TypeError: Cannot call method "getStackTrace" of undefined (rhino.clj#41)^

@mx2000 Have you run the :Piggieback command?

:Piggieback runs okay, but then when i want to eval anything I get this error always

Yes it returns nothing

That error means that :Piggieback isn't working.

What is your full command?

I have in project.clj : :figwheel {:nrepl-port 7888 :nrepl-middleware ["cemerick.piggieback/wrap-cljs-repl" "cider.nrepl/cider-middleware"]}

And first I do :Connect <nrepl://localhost:7888>. Returns. Then :Piggieback

You need to provide :Piggieback with the repl-env

The docs say: If {env} is a number, the piggieback repl-env will will use a cljs.repl.browser (rather than a Rhino) env with the port set to the number provided.

I dont understand, should I just put a new port, or the figwheel browser REPL port?

:Piggieback (figwheel-sidecar.repl-api/repl-env)

This is the full command for figwheel

When you run it, it will block until you open the browser

@mx2000 ^^

CompilerException java.lang.RuntimeException: No such var: figwheel-sidecar.repl-api/repl-env,

@mx2000 Are you on latest figwheel?

https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-with-Emacs-Inferior-Clojure-Interaction-Mode we should create a similar page for vim-fireplace

@markwoodhall Did you settle on anything awesome for your custom :Figwheel command?

@mx2000 let me know if upgrading figwheel works for you.

Yes finally

@mx2000 Only figwheel 0.5.8+ has support for vim

@dominicm Just stuck with what I had for now, if I do have to tweak a bit more I will probably do as you suggested and make :Figwheel accept an optional list of builds to start.

@markwoodhall It would be nice to have that uber command on the figwheel wiki. Would look very pro 😛

Yeah, that would be cool.

I'll put some time into it later, can you show me where you're up to now?

This is all I have at the moment, it’s nothing fantastic. I’ve still got a separate function for running a cljsbuild named “devcards”. https://gist.github.com/markwoodhall/f5c97a93bd7f9d3bf291bad4cec5ac3d Like you said, if you could supply :Figwheel with a list of builds to start that would be cool. I’m not sure if you would still want it to start the default build implicitly as well.

Good question, I'd guess not.

https://github.com/SevereOverfl0w/.files/blob/layers/nvim/layer/clojure/after/ftplugin/clojure.vim#L17-L23 I've done something similar here.

I can do :Boot to run boot cider dev or :Boot repl to run boot cider repl. It's very handy.

Instead of join we'd need something a little more complex, but the idea is the same.

I might have a look later. How do you find boot? I've not looked at it yet!

@markwoodhall it's the bomb, plus a few contributors are vimmers which is why cljs has worked in boot since I used it

Also pods are great

Cool, I really need to take a look. Forgive me….. https://gist.github.com/markwoodhall/a7092991ee2fc0dde5eee9be4b58a00c

@markwoodhall I just had a crazy idea, is there any way to get a list of builds in figwheel?

https://github.com/bhauman/lein-figwheel/blob/master/sidecar/src/figwheel_sidecar/system.clj#L717

Cool!

The completeopts argument is fairly simple, maybe we could get you completion on FigwheelDevcards, without having to hardcode it into the command 🙂

Fig<TAB><SPC>de<TAB> Not quite as short

Still good though

That would be nice!

Good idea.

Be good to hook up (clean-build) and (stop-autobuild) as well.

What you have is pretty good though, you'll realise that all vimscript feels like that, or it does for me

Yeah, it does. I wrote some stuff for a C# plugin that expands completions as snippets on the fly, it was hideous! https://camo.githubusercontent.com/8315b4a3d97cd2bf8e177826cd1be0206aa1fe7f/687474703a2f2f692e696d6775722e636f6d2f594f4153557a542e676966