This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-20
Channels
- # adventofcode (7)
- # announcements (1)
- # aws (1)
- # babashka (127)
- # bangalore-clj (1)
- # beginners (54)
- # calva (8)
- # cider (12)
- # clj-http (2)
- # clj-kondo (8)
- # cljdoc (10)
- # cljs-dev (2)
- # clojure (48)
- # clojure-australia (14)
- # clojure-dev (6)
- # clojure-europe (105)
- # clojure-nl (6)
- # clojure-taiwan (1)
- # clojure-uk (62)
- # clojurebridge (1)
- # clojurescript (112)
- # code-reviews (4)
- # cursive (20)
- # data-science (1)
- # depstar (1)
- # events (8)
- # fulcro (6)
- # graalvm (11)
- # honeysql (2)
- # introduce-yourself (3)
- # jobs (1)
- # jobs-discuss (30)
- # malli (23)
- # nrepl (4)
- # off-topic (47)
- # pedestal (22)
- # polylith (10)
- # portal (3)
- # re-frame (16)
- # reitit (9)
- # releases (3)
- # rewrite-clj (1)
- # ring (1)
- # spacemacs (1)
- # tools-deps (12)
- # xtdb (7)
in run with deps
in aliases it complains that compiler.test.run
is not a valid alias name, because of the dots - but cursive seems happy with it elsewhere.
according to the clojure docs, keywords aren't supposed to contain periods in their name part https://clojure.org/reference/reader#_literals
thanks didn't know that. @U050B88UR can the Clojurescript deps.edn aliases be changed? It seems the names are not valid (keywords containing dots) and Cursive doesn't allow them 😞
Hi.
I tried evaluating (send to repl) (println "\r1111\r222")
and it outputs:
1111
222
whereas in regular clj/clojure
it will output 2221
.
Is there any way to support the \r
character in Cursive REPL?I looked into this issue a while back. Apperantly it's an IntelliJ issue. It might be this one https://youtrack.jetbrains.com/issue/IDEA-147282
The run console is not the same as the REPL console?
I found this answer from 2017: https://stackoverflow.com/a/42473920
> The run console is not the same as the REPL console True, but i figured they might be pretty similar (at least it wouldn't work out of the box). Good find on the SO answer though!
just be prepared for it never being supported 😄 I'm not bashing Cursive/cfleming, there's just a huge backlog of things to do so the ETA for that may be "never"
Sure I agree the backlog is huge. However other people may know it's been requested if nothing else.
It’s sad but true. However there may be a workaround now - Cursive does have some limited support for ANSI codes. I just tested this, and this works in Cursive:
(println (str "Hello" \u001b "[1KWorld"))
However it doesn’t do exactly the same thing in the terminal - in the terminal it erases the Hello with spaces but doesn’t move the caret to the start of the line.
Excellent @U0567Q30W ❤️ Thanks! That's all I need for using progrock