This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (9)
- # aws (1)
- # beginners (133)
- # boot (2)
- # calva (94)
- # cider (48)
- # cljdoc (7)
- # cljsrn (22)
- # clojure (128)
- # clojure-europe (22)
- # clojure-finland (7)
- # clojure-greece (6)
- # clojure-losangeles (3)
- # clojure-nl (81)
- # clojure-spec (30)
- # clojure-uk (60)
- # clojure-ukraine (1)
- # clojurescript (45)
- # core-async (26)
- # cursive (18)
- # datomic (12)
- # defnpodcast (1)
- # duct (4)
- # editors (4)
- # emacs (6)
- # fulcro (37)
- # graphql (4)
- # jobs (2)
- # jobs-rus (1)
- # juxt (7)
- # kaocha (2)
- # leiningen (1)
- # nrepl (22)
- # off-topic (2)
- # re-frame (16)
- # reagent (8)
- # reitit (22)
- # ring-swagger (5)
- # shadow-cljs (81)
- # tools-deps (4)
> @bozhidar hello! many thanks for cider! is there any way to do something like
cider-pprint-eval-last-sexp-to-repl but printing the result in the REPL instead of adding it as input in the REPL?
@stathissideris Do you want just the result printed there? Or you want the form added and the result printed?
["Eval last sexp to REPL" cider-eval-last-sexp-to-repl] ["Eval last sexp and pretty-print to REPL" cider-pprint-eval-last-sexp-to-repl]
cider-pprint-eval-last-sexp-to-repl inserts the result as an expression in the prompt, not above it (or below it)
I don’t think we have something to just display eval results in the REPL, but that’s certainly doable. Why do you need something like this? Won’t it be a bit hard to follow as results would have appeared out of nowhere?
Hi lovely people, do any of you have a
.dir-locals.el file that you use for a combined clj/cljs tools.deps project that you'd be prepared to share with me? i'm not an Emacs user (shoo! shoo!) but I'm trying to set up a build that will work happily with cider jack-in for my colleagues, so i'd really appreciate the help. Thanks!
https://github.com/juxt/edge/blob/master/lib/edge-app-template/resources/clj/new/app.template/dir-locals.el this is the pre-generated one, you'll have to resolve the mustache manually 🙂
yeah, that's fine =D
i saw this, but i guess it's not exactly what i'm after, as it contains (what i understand to be) only a single, global configuration section, whereas i'm after an example with separate
clojurescript-mode sections - or to find i'm barking up the wrong tree?
the long-term thing i'd like to learn is how to set up a clj/cljs project that works for all ides without any custom configuration for each, which means now i need to understand what the custom configuration actually does.
I don't understand what you're looking for with
clojurescript-mode sections, there's nothing to really put in a .dir-locals.el related to them afaik. The bulk of what a cider user is looking for is making jack-in work, after that they want cljs-jack-in to work.
trying to apply a different profile when kicking off jack-in for clojure and clojurescript
jack-in is done to create a single JVM, so the settings have to be shared between them
@bozhidar The workflow I’d like to try is type long multi-line expressions in a .clj file and eval+pretty-print their results in the REPL where the results accumulate. I saw that something similar would be possible with getting the results in a popup buffer, but I prefer to see a “log” of results. If the inputs are also shown (as you said it may be a bit hard to follow otherwise) I think it would be even more usable, but I’d be happy with just the outputs
How do I tell CIDER again not to take over
*err*? My google fu is failing me...
I'm starting my nREPL outside of Emacs, and I want all output to go to that terminal, instead of to the
@stathissideris Got it. It makes sense to me, so I’d suggest filing a ticket about this so I won’t forget to look into it.
> I saw that something similar would be possible with getting the results in a popup buffer,
Yeah, I’m thinking we can probably add another option for the result destinations. I’d be wary of adding dedicated commands for something like this.
I would love the workflow that @stathissideris is talking about. If you are tweaking data, it’s very helpful to have a history that you can just scroll back and see.
can you get this with the insert commands?
> if the eval'ed expression is also added as if it was typed in the prompt of the REPL
check out the map under
C-c C-j for the insert commands
these 1) prevent jumping to the repl buffer on insert and 2) eval it rather than wait for more input
@dpsutton that would actually cover my use case exactly! but I don’t seem to have
works! with a slight problem: it seems that if
cider-switch-to-repl-after-insert-p is true, the REPL scrolls to the end of the result, if it’s
nil it doesn’t 🙂
thanks @dpsutton, I’ll see if I can script it to scroll somehow (didn’t know about the insert commands)