parinfer

dominicm 2017-06-10T08:51:58.641842Z

Could be the part where it replaces the whole file 🙂

dominicm 2017-06-10T09:46:30.785149Z

@shaunlebron is changedLines deprecated?

dominicm 2017-06-10T12:08:57.170098Z

It looks like it was removed as part of the api, but the .js lib is still exposing it

dominicm 2017-06-10T13:28:36.419156Z

@shaunlebron the slowdown is caused by folding searching the entire file after the text changed (to find the closing paren). cc/ @snoe

shaunlebron 2017-06-10T16:31:22.102961Z

@dominicm: reading through the commits, it’s removed for the ‘newline’ fix but I never shipped it

shaunlebron 2017-06-10T16:31:37.103942Z

the changedLines API should still work for 2.0.0

shaunlebron 2017-06-10T16:32:17.106736Z

I’ll back out the unreleased master changes, I’m surprised I put that code in master and not in a branch

shaunlebron 2017-06-10T16:32:57.109213Z

i’ll try to keep it around if you’re using it, not sure if anyone else is

dominicm 2017-06-10T16:34:19.114582Z

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.

shaunlebron 2017-06-10T16:43:45.149933Z

@dominicm does nvim parinfer update on keypress or when entering normal mode like vim-parinfer?

dominicm 2017-06-10T16:53:48.188689Z

@shaunlebron Keypress.