Fork me on GitHub
#cider
<
2019-07-02
>
pinkfrog08:07:32

what’s the difference between so many cider-jack-in ?

practicalli-johnny10:07:33

@i my understanding is that cider-jack-in-clj runs a Clojure repl cider-jack-in-cljs runs a ClojureScript repl cider-jack-in-clj&cljs runs a Clojure repl and then runs a ClojureScript repl

practicalli-johnny10:07:02

I assume cider-jack-in and cider-jack-in-clojure are aliases for cider-jack-in-clj (or perhaps just from older versions of cider). Similarly, I assume cider-jack-in-clojurescript is an alias or older version of cider-jack-in-cljs

bozhidar13:07:59

@jr0cket You’re spot on!

practicalli-johnny13:07:20

Good to know... Thanks

bozhidar13:07:52

We can’t really removed cider-jack-in, as it’s mentioned in way too many places, but probably at some point we’ll remove cider-jack-in-clojure and cider-jack-in-clojurescript, as right now we have a couple of aliases too many. 🙂

bozhidar13:07:25

Btw, fun fact cider is another alias for cider-jack-in-clj.

😀 8
bozhidar13:07:17

At some point I wanted to bring the names more in line with SLIME’s, but it seemed people like to jack-in, so I didn’t push much on that front.

practicalli-johnny13:07:04

jack-in always reminded me of the cyberpunk books by William Gibson, that's why I liked the term

bozhidar13:07:34

Ah, my bad - actually after I dropped the idea I made M-x cider an unified entry-point for all commands.

nwjsmith16:07:38

:thinking_face: I’m getting user-error: No reader for tag #function in (inst uuid) when running tests

nwjsmith16:07:23

My .nrepl.edn file looks like {:middleware [cider.nrepl/cider-middleware]}

nwjsmith16:07:34

oh, looks like that’s not enough. Might have to use cider-nrepl-handler

ghadi17:07:28

how are you starting those tests? and are you on 1.10.1 @nwjsmith?

nwjsmith17:07:22

{:major 1, :minor 8, :incremental 0, :qualifier nil}

nwjsmith17:07:40

Is there a #function tag in 1.10?

ghadi17:07:50

that's a CIDERism

nwjsmith17:07:52

Here’s what I’m trying to do: I have a Clojure application that embeds its own nREPL server. This application run inside a Docker container. I would like to have CIDER’s middleware included into the embedded nREPL server by mounting an .nrepl.edn file and a .lein/profiles.clj file.

nwjsmith17:07:52

The application is launched with lein run.

dpsutton17:07:01

> • [Abbreviated printing](https://github.com/clojure-emacs/cider-nrepl/pull/268) for functions multimethods. Instead of seeing #object[clojure.core$_PLUS_ 0x4e648e99 "clojure.core$_PLUS_@4e648e99"] you'll see #function[clojure.core/+]. that one's new to me

dpsutton17:07:05

does this help @nwjsmith

(when @env/dev?
      (nrepl.server/start-server :bind "0.0.0.0" :port nrepl-port
                                 :handler cider-nrepl-handler)
      (println "[INIT] nrepl started on port" nrepl-port))
this is from our work codebase

dpsutton17:07:28

inside docker. (also there's a docker-translate-paths PR to CIDER out there you should try out as well)

nwjsmith17:07:46

That docker-translate-paths PR looks extremely useful, thanks!

nwjsmith17:07:41

@dpsutton unfortunately there isn’t any “dev” environment for this application, so that won’t quite work. I’m going to do some digging to see if handler is configurable with nrepl.edn

oskarkv18:07:44

@dpsutton Did you get a chance to look at those issues?

dpsutton18:07:19

I did. Commented on thread

oskarkv18:07:27

Hm, what thread? 😛

oskarkv18:07:27

Oh, thanks

diego.videco23:07:26

Does anyone experience, after clearing the repl buffer (`cider-clear-repl-buffer`), that logs will not appear until one scrolls upwards? Any idea how to fix this so that logs will still appear without having to scroll?

oskarkv23:07:36

When you say "logs" you mean like printlns? I can see them without any scrolling.

diego.videco23:07:14

yes printlns and variations of that

carkh23:07:55

yes there appears to be some "drift" over time

carkh23:07:07

but clearing fixes it for me