Brian Hurlow
Brian Hurlow
@midnio can you provide more info on your use case? I believe that "paren" mode may be deprecated in favor of "smart" mode coming in future versions
@metasoarous yea, noticing the same thing. The VimL implementation is very very slow, so I think https://github.com/bhurlow/vim-parinfer/issues/35 would probably be a big improvement
In the first release I actually sent the buffer over the wire to a node.js server running the parinfer js lib and that was also considerably quicker
@metasoarous are you using neovim or regular vim?
@eraserhd can't wait to try it
@metasoarous yes I have seen this and it's annoying as hell! I think it has to do with finding the 'top level form'
ahhh yes, I knew something mysterious had changed. This makes sense. Seems like some option to bypass the undo history is what we need, this is outside my immediate vim...
@jschomay thanks for digging! Ideally we could so something like ~~ `TextChanged() && !undoAction`
I'm interested by the thought of storing a separate set of changes related to CLJ editing, i.e. the undo could restore at the structural level rather than a single paren....
@spinningarrow noted 😢