Fork me on GitHub
#cider
<
2018-02-19
>
bozhidar03:02:49

No, there is not.

bozhidar03:02:58

As for the previous discussion - without having some session mechanism for REPL connections you can’t really have one session for evaluation and one for tooling commands. We discussed this with Alex Miller around the time the socket REPL was introduced.

bozhidar03:02:49

inf-clojure can’t just create two REPLs sharing nothing, because if they don’t share nothing they obviously don’t share the state of your application. 😉

bozhidar03:02:22

It would have been nice if Clojure had some wrapper macro, in which, evaluations don’t affect *1, *2, etc.

bozhidar03:02:34

On a related note - probably inf-clojure deserves its own channel or something. Seems all of the discussions regarding it are happening here and in #emacs.

bozhidar03:02:51

On the other hand - this Slack has no history which completely sucks…

dpsutton03:02:45

which channel do you want it to vanish from 🙂

dpsutton03:02:58

although having a dedicated channel might improve its visibility a little?

ghadi03:02:09

I don't follow this statement at all.

ghadi03:02:34

created #inf-clojure

qqq05:02:30

I'm not a paying user of slack; but I don't get people's reluctance to pay slack if they find the history useful

gonewest81807:02:34

As far as I know individuals can’t opt-in to history; it’s enabled across the entire community. Therefore you need everybody to agree to pay, because effectively it’s seancorfield paying Slack $8*N per month (where N>10000) and everybody else paying him.

qqq09:02:21

Ah, if everyone has to pay for anyone to get access to history, it's a different issue. I misunderstood. Thanks for clarifying.

bozhidar10:02:50

Yeah, exactly. The team has to be paying, not individuals.

bozhidar10:02:23

Right now a ton of great conversations disappear all the time…

qqq12:02:35

so if the situation is, "unless Clojurians pay $80,000 / month, no one can see history in slack", then it is quite a problem

qq00:02:51

It has been discussed few times with few alternatives (Discord is probably a viable choice), if I remember correctly, the core members ultimately choose neither to move out anywhere else anytime soon nor to pay slack. :thinking_face:

bozhidar10:02:34

@ghadi Well, in REPL one you’ve evaluated a few definition forms, in the other REPL you want to get a list of all vars (or whatever) - if they didn’t share the application state how is this supposed to work?

ghadi20:02:04

REPLs share the application. different sockets may be in different *ns*es

ghadi20:02:13

alex's example used an atom+custom eval to share bindings across connections. I don't think this is needed for a basic tool (like inf-clojure)