Ok, figured this out. I had to add the option to pass in a *:url* to the * repl-env* function. Made a pull request here<https://github.com/cemerick/austin/pull/19>. Let me know if you'd like anything changed or cleaned up.
Thanks Tim Washington Interruptsoftware.ca / Bkeeping.com On Fri, Oct 11, 2013 at 7:52 PM, Timothy Washington <[email protected]>wrote: > This looks awesome. I'm digging into it right now. > > *A)* A problem cropped up where the example app, provided > here<https://github.com/cemerick/austin/blob/master/browser-connected-repl-sample/README.md>, > isn't working for me. After *i)* turning off all other repls and > *ii)*following instructions exactly, the call to > *(js/alert "Salut!")* just hangs. However, my environment is behind a *VM > Ware Guest* Ubuntu Linux (OSX Host). So I don't know if this is > interfering with the setup, in any way. > > *B)* That being said, I can't wait to dig more into this. As far as > feedback and requests goes, for the longest while, I've wanted *nrepl-ritz > * / *nrepl.el* / *cljsbuild auto* / *cljsbuild repl-listen* ... in same > session (see > here<https://groups.google.com/forum/#!topic/clojure/kc3jQvKmLHg>). > This meaning, that I've wanted cljs auto-build that tees both to the file > system, and the browser connected repl. Also, a debugger would be available > if any Clojure errors pop up. I believe you'd need *cljsbuild auto* and > *cljsbuild > repl-listen* setup as nrepl middleware. But I'm by no means an expert. > > > Cheers. Great work. > > Tim Washington > Interruptsoftware.ca / Bkeeping.com > > > On Mon, Sep 9, 2013 at 8:24 PM, Nelson Morris <[email protected]>wrote: > >> I've been using austin on a project with emacs/nrepl. It works for a C-c >> C-k, switch to nrepl, interact with app. However, some other features like >> auto-complete and jump-to-symbol-definition I'm used to in a clojure >> workflow don't work or cause a core to spin. I'd suspect the eldoc call to >> show the function arguments could act similar. >> >> - >> Nelson >> >> >> On Mon, Sep 9, 2013 at 10:25 AM, Norman Richards >> <[email protected]>wrote: >> >>> On Mon, Aug 5, 2013 at 8:21 AM, Chas Emerick <[email protected]> wrote: >>> >>>> As you might know, I've been tinkering with an easier-to-use variant of >>>> ClojureScript's browser-REPL for some time. I've finally wrapped that up >>>> into its own project, Austin: [...] >>>> >>> >>> >>> Is anyone successfully using this with nrepl in emacs? I am able to >>> make it work, but something is causing both emacs and the JVM it is >>> connected to to use 100% CPU. I seem to be getting a long stream of >>> "Unable to resolve symbol: if-let in this context, >>> compiling:(NO_SOURCE_PATH:1:1)" >>> >>> See: https://gist.github.com/orb/6496320 >>> >>> *nrepl-connection* fills up with: >>> >>> d2:ex45:class >>> clojure.lang.Compiler$CompilerException2:id6:1504207:root-ex45:class >>> clojure.lang.Compiler$CompilerException7:session36:43e688aa-01c2-4824-b1f3-1bd05a1f02446:statusl10:eval-erroreed3:err128:CompilerException >>> java.lang.RuntimeException: Unable to resolve symbol: if-let in this >>> context, compiling:(NO_SOURCE_PATH:1:1) >>> >>> >>> I'm not sure if this is a problem with austin or if it's nrepl.el or >>> something on the emacs side. >>> >>> As a side note, I occasionally get a similar error message using >>> straight nrepl when first starting up, but it usually only happens once. >>> With austin/nrepl it appears to be stuck in some kind of loop erroring >>> over and over... Does anyone have a known good setup I could try to >>> reproduce? >>> >>> -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
