This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-10
Channels
- # aleph (1)
- # beginners (39)
- # boot (14)
- # cider (2)
- # clara (6)
- # cljs-dev (39)
- # cljsrn (2)
- # clojure (276)
- # clojure-italy (1)
- # clojure-russia (22)
- # clojure-sg (2)
- # clojure-spec (7)
- # clojure-uk (9)
- # clojurescript (47)
- # core-async (1)
- # cursive (5)
- # emacs (1)
- # events (3)
- # leiningen (1)
- # luminus (2)
- # lumo (75)
- # om (14)
- # onyx (1)
- # parinfer (11)
- # pedestal (1)
- # ring-swagger (2)
- # spacemacs (4)
- # untangled (5)
- # yada (29)
@shaunlebron is changedLines deprecated?
It looks like it was removed as part of the api, but the .js lib is still exposing it
@shaunlebron the slowdown is caused by folding searching the entire file after the text changed (to find the closing paren). cc/ @snoe
@dominicm: reading through the commits, it’s removed for the ‘newline’ fix but I never shipped it
the changedLines API should still work for 2.0.0
I’ll back out the unreleased master changes, I’m surprised I put that code in master and not in a branch
i’ll try to keep it around if you’re using it, not sure if anyone else is
I'm not now I figured out that the bug was vim related, not a bug in nvim parinfer 🙂. It does seem like a good way to update large buffers though. But it doesn't seem to have been an issue yet.
@dominicm does nvim parinfer update on keypress or when entering normal mode like vim-parinfer?
@shaunlebron Keypress.