This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-17
Channels
- # arachne (1)
- # beginners (42)
- # boot (4)
- # cider (28)
- # clara (9)
- # cljs-dev (149)
- # cljsrn (5)
- # clojure (185)
- # clojure-austin (2)
- # clojure-dusseldorf (4)
- # clojure-italy (14)
- # clojure-norway (1)
- # clojure-russia (18)
- # clojure-spec (35)
- # clojure-uk (36)
- # clojurescript (78)
- # core-async (6)
- # data-science (20)
- # datomic (48)
- # emacs (1)
- # fulcro (2)
- # garden (4)
- # hoplon (47)
- # jobs (5)
- # jobs-rus (1)
- # leiningen (2)
- # lumo (12)
- # off-topic (8)
- # om (8)
- # onyx (39)
- # parinfer (19)
- # re-frame (100)
- # reagent (15)
- # ring-swagger (1)
- # sql (8)
- # vim (1)
- # yada (20)
@shaunlebron Is there some discussion in parinfer issues about smart mode dropping to paren mode that I could look at? I’m particularly interested in releaseCursorHold
.
@cfleming yeah, this was the whole issue around dedenting in smart mode
i think some people expected “stickiness” behavior when dedenting
(println {:a 1
:b 2}
bar)
deleting println should not cause bar
to be absorbed into the map since the user could be typing something else
right, replacing println with foo without stickiness would allow:
(foo {:a 1
:b 2}
bar)
whereas stickiness would align bar with the map
the stickiness is an alternate solution that I didn’t go with
stickiness means bar
would be immediately dedented the moment the map reaches it
and would “stick” to it afterwards when foo
pushes it forward
but what you’re saying is right, if println
is deleted, bar
is dedented if cursor moves away without adding foo
if you want all the hairy details: https://github.com/shaunlebron/parinfer/issues/143
Right, I see how that works. And that’s because paren mode is run on releaseCursorHold.