Fork me on GitHub
#parinfer
<
2017-06-10
>
dominicm08:06:58

Could be the part where it replaces the whole file 🙂

dominicm09:06:30

@shaunlebron is changedLines deprecated?

dominicm12:06:57

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

dominicm13:06:36

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

shaunlebron16:06:22

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

shaunlebron16:06:37

the changedLines API should still work for 2.0.0

shaunlebron16:06:17

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

shaunlebron16:06:57

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

dominicm16:06:19

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.

shaunlebron16:06:45

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

dominicm16:06:48

@shaunlebron Keypress.