Could be the part where it replaces the whole file 🙂
@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.