This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-03
Channels
- # arachne (31)
- # aws (9)
- # bangalore-clj (7)
- # beginners (46)
- # boot (18)
- # cider (21)
- # cljs-dev (8)
- # clojure (154)
- # clojure-dusseldorf (5)
- # clojure-filipino (3)
- # clojure-ireland (4)
- # clojure-italy (9)
- # clojure-russia (6)
- # clojure-spec (6)
- # clojure-uk (52)
- # clojureremote (3)
- # clojurescript (173)
- # clojurewest (14)
- # cursive (24)
- # data-science (2)
- # datomic (18)
- # defnpodcast (1)
- # devcards (1)
- # hoplon (4)
- # instaparse (29)
- # jobs (2)
- # juxt (1)
- # leiningen (3)
- # lumo (78)
- # off-topic (46)
- # om (9)
- # onyx (42)
- # pedestal (33)
- # perun (3)
- # re-frame (9)
- # reagent (6)
- # slack-help (5)
- # spacemacs (2)
- # specter (6)
- # unrepl (157)
- # untangled (99)
- # yada (32)
@rauh https://github.com/cursive-ide/cursive/issues/1701, so I don’t forget
@nxqd Sorry, I missed your message - that means that the module you’re loading that code from isn’t on the classpath of your REPL
@cfleming Sounds good, let me know if I can help. I could probably log the repl msgs in a custom nrepl server.
I’m not sure that’s possible, you might have to do it programatically in a file and load that file on your repl/jar like as a source
https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-in-a-Cursive-Clojure-REPL
@tjtolton Having that be automatic for Figwheel (not arbitrary plugins) is coming soon
So I have this modified so that the namespace is stored in the REPL history, and is used by REPL commands and also the REPL history search.
The question is what to do with commands which are entered in the REPL editor window, and are implicitly executed in the current REPL namespace.