Fork me on GitHub
#cider
<
2018-03-08
>
bozhidar01:03:46

I’ve wrote that library in Emacs, so I can tell you that’s not a big deal. 😄

bozhidar01:03:07

It’s a bit more efficient to do it as mentioned there, but it’s confusing for many people reading the code afterwards. The reason for the recommendation is that everything’s implemented in terms of macros and inline functions that are expanded during the compilation phase, so in the end you don’t really end up including any new definitions from there.

gganley01:03:33

Thank you for the explanation

macrobartfast05:03:04

when M-x cider-grimoire getting "Bad url: /" ... help

macrobartfast05:03:26

can't seem to resolve the issue.

bozhidar05:03:13

Works just fine for me. How are you getting this error?

macrobartfast05:03:26

in a clojure file, while pointer is in, say, the word conj, invoking cider-grimoire via M-x cider-grimoire, which causes "Grimoire doc for (default conj):" to appear in the minibuffer... accepting the default by hitting enter produces in the minibuffer "Bad url: /" .

macrobartfast05:03:00

I didn't find this error mentioned much while searching online, so not sure what's up.

macrobartfast05:03:58

if I supply a different string for it to search grimoire for at the prompt, I get the same result.

bozhidar05:03:10

What’s your Em. acs version? I’m on 25.2

macrobartfast05:03:54

grimoire did work once, if I recall right

macrobartfast05:03:00

in this version, I mean.

macrobartfast06:03:59

well, an obscure one relating to some strange state in my system, no doubt.

macrobartfast06:03:14

and no really critical, as I can just look it up in a browser.

macrobartfast06:03:33

but thought I'd bounce it off #cider to see if anything sprang to mind here.

bozhidar07:03:51

I don’t know - seems to me something like this should work just fine on 24.5 as well.

xiongtx20:03:33

Here’s an interesting 🐛: https://github.com/clojure-emacs/cider/issues/2233 We may even kill 2 🐦s w/ 1 :curling_stone: if this is the cause of #1936 as well: https://github.com/clojure-emacs/cider/issues/1936

xiongtx00:03:03

@ @gonewest818 If you could reproduce and confirm, that’d be great. Want to make sure I’m not 🔩s

gonewest81800:03:18

confirmed. I can reproduce that too. I’m using Emacs 25.3 and cider 0.17.0-snapshot.

mathpunk21:03:05

I'm interested in trying to use custom/multiple REPLs to interact with processes, after a Stuart Halloway talk last year. It appears that's not possible in my current dev environment due to https://github.com/clojure-emacs/cider/issues/2017

mathpunk21:03:46

is there anything I can do to help with this bug? or, should I be looking into changing up my environment, like using inf-clojure or something?

mathpunk21:03:31

for the record, I'm getting identical behavior

richiardiandrea22:03:13

Inf-clojure might be a better tool for that because it does not assume anything I guess, have you tried with that?

mathpunk22:03:02

@richiardiandrea Not yet. Since my spacemacs/CIDER set-up "Just Works" for most stuff I've been trying to avoid getting into devtooling

mathpunk22:03:11

but, it can't always be avoided 🙂

richiardiandrea22:03:15

Ah! Especially with Emacs 😺

gonewest81823:03:41

I can’t quite tell if this accomplishes what you need, but you can start a tools.nrepl server on a different port and get a second repl connection using M-x cider-connect.

user> (require 'clojure.tools.nrepl.server)
nil
user> (clojure.tools.nrepl.server/start-server :bind "localhost" :port 9999)
#clojure.tools.nrepl.server.Server{:server-socket #object[java.net.ServerSocket
                                                          "0x6200214e"
                                                          "ServerSocket[addr=localhost/127.0.0.1,localport=9999]"],
                                   :port 9999,
                                   :open-transports #object[clojure.lang.Atom
                                                            "0x3af6099b"
                                                            {:status :ready,
                                                             :val #{}}],
                                   :transport #object[clojure.tools.nrepl.transport$bencode
                                                      "0xf75b0f8"
                                                      "[email protected]"],
                                   :greeting nil,
                                   :handler #object[clojure.tools.nrepl.middleware$wrap_conj_descriptor$fn__5306
                                                    "0x69ee663f"
                                                    "[email protected]e663f"],
                                   :ss #object[java.net.ServerSocket
                                               "0x6200214e"
at this point you can M-x cider-connect to port 9999 and have two separate repls into your server process. In practice you need to keep the object returned from start-server (I let it print to the repl so you could see), because that’s the object you pass to stop-server when done.

mathpunk23:03:18

@gonewest818 Cool thanks! I will at the very least file it with my notes on the topic, as I haven't exactly decided what I'm going to do with sub-repls, just that they seem like an interesting way to attack a class of problems