This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-10
Channels
- # announcements (14)
- # beginners (55)
- # calva (4)
- # cider (9)
- # clojure (56)
- # clojure-austin (25)
- # clojure-brasil (1)
- # clojure-dev (29)
- # clojure-europe (44)
- # clojure-mexico (1)
- # clojure-nl (2)
- # clojure-norway (1)
- # clojure-uk (5)
- # clojurescript (15)
- # cursive (9)
- # datomic (5)
- # emacs (30)
- # events (1)
- # graalvm (30)
- # honeysql (17)
- # hyperfiddle (54)
- # introduce-yourself (1)
- # jobs-discuss (6)
- # kaocha (2)
- # leiningen (5)
- # lsp (6)
- # malli (3)
- # missionary (16)
- # off-topic (42)
- # overtone (40)
- # pedestal (2)
- # re-frame (21)
- # shadow-cljs (16)
- # squint (2)
- # tools-deps (14)
when I select something from repl history, the form is immediately executed - this is pretty often not what i want.. any way to turn the execution part off?
if you mean the repl history window, there's a note at the bottom that says "shift + enter to copy to REPL window", and that doesn't execute immediately... is that what you're looking for?
I've accidentally executed stuff that I just wanted to copy I don't know how many times now, slowly getting used to SHIFT+ENTER, but I think ENTER = copy to REPL would have been a safer default. However, swapping them now would also be confusing, since a bunch of people that have now gotten used to SHIFT+ENTER would then get the statement executed.... cc: @U0567Q30W
This originally was reversed, but I changed it because the community has pretty clearly moved to primarily executing code directly from files rather than typing into the REPL. In particular, when a form is sent from a file to the REPL then it’s executed in the namespace of the file rather than the current ns of the REPL. By copying the form to the editor to later be submitted, you lose the ability to do that.
Okidoki! For me it's more commmon to modify the form before executing it, but of course you'll have to go with how the majority work.
Is there a way to disable the monkey-patching of clojure.test/report
? I've added a method to it for our custom error assert-expr
, and it's not being used
I’m afraid not, if you want to use the Cursive interactive testing, since that’s basically how it works.
Okay, thanks