Fork me on GitHub
#parinfer
<
2017-07-30
>
shaunlebron02:07:56

@rgdelato i’m pairing with chris in 20 minutes to get v3 in atom, would you like to join?

rgdelato02:07:12

sorry, I'm actually out right now, won't be home for at least an hour or two

shaunlebron02:07:15

i wonder if we can pair while streaming somehow

shaunlebron02:07:28

np, late notice

mattly03:07:19

I might have to give Atom another shot

cjhowe04:07:38

btw, gave parinfer with paredit a try, i think there are many cases that don't work well (especially with slurp and barf)

cjhowe04:07:24

especially because parinfer lets you get loosey goosey with the parens, but then that break paredit

cjhowe04:07:53

i'll try to document the cases i come across

cjhowe05:07:01

i honestly think it's paredit's fault though

henrik05:07:55

Man, it’s like cljs christmas at the moment. New version of cljs the other day and now soon parinfer v3 in Atom.

cjhowe05:07:13

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)

cjhowe05:07:31

(can confirm this exact case doesn't happen without parinfer mode on, which seems like a very weird bug honestly)

cjhowe05:07:44

gonna try smartparens to give me that functionality instead

shaunlebron06:07:43

@cjhowe thanks for reporting this

shaunlebron06:07:06

i don’t understand what “slurping before” means

shaunlebron06:07:54

and I don’t understand the description of what happened—can you show what the “after” state is?

cjhowe07:07:42

@shaunlebron i'll report in a gh issue if that's okay?

shaunlebron15:07:10

@cjhowe sounds good, thanks!