This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-04
Channels
- # announcements (1)
- # architecture (18)
- # aws (7)
- # babashka (63)
- # beginners (38)
- # bristol-clojurians (1)
- # circleci (1)
- # clj-kondo (10)
- # clojars (4)
- # clojure (159)
- # clojure-berlin (3)
- # clojure-europe (4)
- # clojure-italy (7)
- # clojure-losangeles (6)
- # clojure-nl (7)
- # clojure-spec (3)
- # clojure-uk (109)
- # clojurescript (54)
- # css (1)
- # cursive (38)
- # data-science (2)
- # datascript (3)
- # datomic (14)
- # docker (2)
- # duct (11)
- # fulcro (47)
- # jobs (8)
- # jobs-discuss (3)
- # kaocha (4)
- # malli (3)
- # nyc (2)
- # off-topic (30)
- # overtone (3)
- # re-frame (17)
- # reagent (33)
- # shadow-cljs (29)
- # spacemacs (3)
- # specter (4)
- # tools-deps (13)
- # xtdb (13)
It seems my new projects are now all called "Imported From Deps". Can I change this to match the directory name?
Changing that and then reopening the project updated the name. I think Cursive used to set the parent name to the directory name though.
Yeah, that seems to have changed in 2019.3. Are you creating the projects in IntelliJ, or creating using the CLI and then importing?
I'm finding Intellij 2019.3.1 and 2019.3.2 painfully slow, anyone else the same? To be clear I don't think it's a Cursive issue (though I guess it's possible). Super laggy scrolling through cljs files in the editor pane, super unresponsive with shortcut keys, seems to take forever to gain focus when switching into app. I'm fairly certain it's since I bumped up to 2019.3.x in early january.
That's my experience as well.
I was noticing that yesterday too, I've disabled almost all plugins too 😞
I’ve noticed IntelliJ being laggy too, but it’s always difficult to tell on my dev machine since I run multiple instance of IntelliJ and debug a lot.
I can imagine that your Intellij setup might be a bit bonkers Colin! I'm putting it down to suuuuper poor performance regression since the 2019.3.1 update.
Worst bug report ever, like when I went to the doctor at Uni and said "I'm just like, suuuuuper tired".
Is there a bindable command to show expected/actual difference after a failed test run? I would love not having to hover-scroll-click
i started using F2 for that purpose actually. discovered it accidentally 🙂 it's jumping to other locations too, but includes this use-case too
I do have that bound, and it does bring up the hover window, however inside the hover window there's a link at the bottom saying "Show difference". When you click that, it will show the diff in Idea's diff viewer which is quite handy for large diffs. I'm looking for a way to invoke "Show difference" with the keyboard
Yeah, that show difference action was not exposed as a bindable function the last time I asked about it a few months ago.
One of our customers was asking about debugging a long ->> pipeline, and I suggested to comment out all the steps he didn’t want to run, but a step that called tap> would be more useful
Dunno, the easy thing would be to print the data to the repl but you can already do that today
Yeah, I’m planning on adding a data inspector so that might be a good candidate. My socket REPL support is sort of prepl-y but also has structured input, so I could potentially do things with tap values on the Cursive side there too
i just use the dbg
macro from this library usually:
https://github.com/philoskim/debux#debugging-thread-macro-or
If I (:require [clojure.test :as t]) in a -test.cljs file, Cursive marks 't' as unused--even when t is clearly used. If, instead, I (:require [cljs.test :as t]), then Cursive doesn't complain.
I’m using tools.deps with Cursive. I have the following alias that I’m trying to use with the cursive repl.
{:repl {:main-opts ["-i" "aot.clj" "-r"]}
Someone mentioned this to me a while back. I thought I had investigated but I can’t find my notes now. I’ll take another look.
Thanks @U0567Q30W, let me know if I should file an issue.