This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-30
Channels
- # aleph (4)
- # beginners (24)
- # boot (15)
- # cider (4)
- # cljs-dev (37)
- # clojure (73)
- # clojure-losangeles (1)
- # clojure-serbia (1)
- # clojure-spec (27)
- # clojurescript (78)
- # core-logic (3)
- # datascript (9)
- # datomic (10)
- # events (1)
- # lein-figwheel (1)
- # lumo (2)
- # off-topic (14)
- # om (6)
- # om-next (1)
- # parinfer (18)
- # pedestal (2)
- # protorepl (4)
- # re-frame (2)
- # reagent (56)
- # specter (6)
- # unrepl (2)
@rgdelato i’m pairing with chris in 20 minutes to get v3 in atom, would you like to join?
i wonder if we can pair while streaming somehow
np, late notice
btw, gave parinfer with paredit a try, i think there are many cases that don't work well (especially with slurp and barf)
especially because parinfer lets you get loosey goosey with the parens, but then that break paredit
Man, it’s like cljs christmas at the moment. New version of cljs the other day and now soon parinfer v3 in Atom.
for example, slurping before the "(:red ...)" form in this causes it to slurp the comment... which normally wouldn't happen with paredit
#_[(:red (:bold "testing"))
"more"
(:green "text")]
;; after using slurp before the (:red ...) form, becomes part of the #_[] form (with the trailing ] in the comment)
(can confirm this exact case doesn't happen without parinfer mode on, which seems like a very weird bug honestly)
@cjhowe thanks for reporting this
i don’t understand what “slurping before” means
and I don’t understand the description of what happened—can you show what the “after” state is?
@shaunlebron i'll report in a gh issue if that's okay?
@cjhowe sounds good, thanks!