This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-12
Channels
- # aws (3)
- # beginners (28)
- # boot (3)
- # cider (28)
- # clara (5)
- # cljs-dev (107)
- # cljsrn (1)
- # clojure (40)
- # clojure-austin (2)
- # clojure-brasil (5)
- # clojure-canada (1)
- # clojure-italy (1)
- # clojure-spec (39)
- # clojure-uk (38)
- # clojurescript (33)
- # community-development (11)
- # cursive (11)
- # datomic (43)
- # duct (6)
- # emacs (7)
- # flambo (1)
- # fulcro (68)
- # graphql (11)
- # jobs (1)
- # jobs-discuss (8)
- # leiningen (16)
- # luminus (2)
- # lumo (1)
- # off-topic (38)
- # om (2)
- # onyx (15)
- # parinfer (32)
- # portkey (5)
- # re-frame (50)
- # reagent (50)
- # reitit (1)
- # shadow-cljs (63)
- # spacemacs (10)
- # sql (27)
- # unrepl (6)
- # yada (2)
did something new roll out? i’m guessing i get updates automatically right?
@drewverlee a dev build for new parinfer version. see here: https://groups.google.com/d/msg/cursive/ZJ4fcp3A988/VVw9I2_pAwAJ
you will not automatically get it yet
ok, I found it
@cfleming: tried out the incorrect-indentation markings by loading up the clojurescript compiler repo
three bits of feedback: - I like the annotation when hovering over the red marks - difficult to go to the next incorrect indentation to fix - I expected to be able to click the “parinfer cannot run based on incorrect indentation” status message at bottom right to show the invalid location - speed is bad on a 11k file
video if you want to see it: https://www.youtube.com/watch?v=UBf56R1DTpM
F2 should jump to the next indentation marker - that’s the standard IntelliJ “Go to next problem”
Re: Clicking on the status message - I don’t think IntelliJ users would expect to be able to do that (you can’t on most hints). I’ll think about a way to allow jumping to the problem - perhaps just a reminder that F2 will do it.
definitely do what’s idiomatic to the editor