This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-10
Channels
- # announcements (5)
- # aws (18)
- # babashka (1)
- # beginners (81)
- # calva (7)
- # chlorine-clover (1)
- # cider (5)
- # cljs-dev (8)
- # clojure (125)
- # clojure-dev (1)
- # clojure-europe (31)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-norway (1)
- # clojure-spec (5)
- # clojure-sweden (1)
- # clojure-uk (31)
- # clojurescript (85)
- # code-reviews (1)
- # core-async (17)
- # cursive (39)
- # datomic (16)
- # emacs (1)
- # fulcro (6)
- # java (16)
- # kaocha (2)
- # luminus (4)
- # malli (2)
- # off-topic (65)
- # pathom (3)
- # re-frame (11)
- # reagent (5)
- # remote-jobs (1)
- # rum (5)
- # sci (10)
- # shadow-cljs (24)
- # spacemacs (4)
- # test-check (3)
- # tools-deps (22)
- # xtdb (15)
Noticed that IDEA becomes completely unresponsive when running a test which fails and then hovering on the test to get diff and diff happens to be large
i don't think this is a cursive-specific problem. intellij idea, in general, hangs when rendering large amount of text.
you can try this by converting that edn data to json and paste it into a json scratch file.
Maybe Cursive could detect that this amount of text will hang the ide and not render it.
It think it would be better to say that can’t show diff because it is too large than to hang the whole IDE 😉
Hi! Cursive tells me
> thrown-with-msg? cannot be resolved
for (deftest ... (is (thrown-with-msg? ...))) (I do require [clojure.test :refer :all]) Is this a known problem or do I do something wrong? The code runs just fine.
I just (declare ...) it so the warning disappears. Your require is right and you're not doing anything wrong 🙂
thrown-with-msg? is not something you can import, it's clojure test macro "magic"
This comment is interesting : https://github.com/clojure/clojure/blob/28efe345d5e995dc152a0286fb0be81443a0d9ac/src/clj/clojure/test.clj#L472
You can extend clojure.test thanks to the assert-expr multimethod.
ok, thanks! I expected Cursive to have some special support for the built-in stuff in clj test. Nice trick with declare!
@danvingo if your machine is a recent one you might have bumped into an CPU bug in icelake: https://www.techpowerup.com/268479/intel-ice-lake-cpus-have-a-system-crashing-bug
pretty shit luck this year - the linux machine was the dell xps dev edition laptop with a 4k screen. I spent about a week scouring the intellij forums and that issue showed up, so that was my best guess, but could have been some other hardware issue. I returned that and got the macbook only to have it crash as well. I'm looking at a thinkpad next...
you are just going to trade hw your issues with a different set of ones, which you will have probably even less info about on the internet >;D
yep... I'm going to try emacs on the macbook for a while and see if there are any issues, the more time others can find and fix the issues on the new hardware the better 😄
@cfleming I need this in my life (with editor support 🙂): https://twitter.com/cgrand/status/1281527501387440128
I just recently rewatched https://youtu.be/kt4haSH2xcs from you and wondering if there are any plans to extend the macro support
So, yes, there are, but unfortunately there’s a somewhat large refactor I have to do first, and I never get to it.
That talk is impressive. I saw it a few years ago and got there again reading the clj-kondo macro thread on clojureverse. It would be really nice to see an alternative approach emerge.
Thanks! I think that talk was one of the original motivations for spec - Rich came up and talked to me quite a bit about it afterwards.
I’m actually planning to (finally!) get the error-marking part of that in Cursive soon, based on a new parser I wrote a while back. That will allow a lot of nice things, like context-sensitive completions.