This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-11
Channels
- # aleph (5)
- # beginners (13)
- # boot (2)
- # cljs-dev (1)
- # clojure (12)
- # clojure-italy (1)
- # clojure-russia (67)
- # clojure-uk (2)
- # clojurescript (49)
- # datomic (1)
- # defnpodcast (3)
- # graphql (8)
- # jobs (1)
- # lein-figwheel (1)
- # leiningen (1)
- # lumo (9)
- # off-topic (5)
- # om (3)
- # parinfer (13)
- # pedestal (2)
- # re-frame (5)
- # reagent (4)
- # ring-swagger (2)
- # untangled (13)
- # yada (2)
@dominicm does it also only consider the parent form (like atom-parinfer) or the whole file?
@spinningarrow it does whole file as of yesterday, but he’s looking into doing only parent form I believe
Ah okay
Ah okay
I was playing with vim parinfer - in vim8 there are some autocommands we can use to call parinfer even in insert mode
TextChangedI I think it was
@spinningarrow yeah, TextChangedI is what is used.
@shaunlebron during rewriting, I did a profile. On the whole file (1.3k) parinfer was near-instant. Like, so fast. The slow down was writing to the buffer, which I fixed by turning off code folding (the click to collapse feature in most ides)
Trying to do top-level form detection is difficult. I looked at atom-parinfer's implementation & read surrounding issues, it's a bit of a hack with edge case concerns. As parinfer on whole file is fast already, I didn't bother.
@dominicm ah nice, do you mean in neovim or vim?
@spinningarrow in Neovim.
Right. I was talking about trying to do the same for vim-parinfer as well; encouraging to know that that's how neovim-parinfer does it as well!
@dominicm nice! i’ll install it today and give it a try