Jason Felice
Jason Felice
Hi! It looks like there are tabs in the original, and neither the original parinfer implementation, nor this one, supports them well (they both replace the tabs with exactly two...
Regarding the examples using comments, I think that parinfer should have some special logic to keep the brackets after the comments, and this would include moving brackets down when a...
@andreyorst It's an interesting thought. I'm not really sure it's possible, as I'd have to think through a bunch of cases. If you want to go through the JSON test...
Interesting! Thanks for reporting (I have been wondering where the spaces have been coming from but haven't had a chance to investigate.) This seems to be interplay between what parinfer...
Hi! There's a couple of possibilities. It *looks like* `g:parinfer_mode` has been changed. When it's "paren", it will not fix parens (because it fixes indentation), and this will affect any...
@uosl Do you have an idea what might be triggering the mode change?
Nice, thanks for finding this! Yes, parinfer should definitely not try to modify a read-only buffer. I'm going to re-open this issue and update the title.
Closing, as this is definitely a duplicate of #14.
After closer inspection, this is a separate issue. I can't reproduce on Vim 8.2.1522, but I have suspicions about what is happening. Next time it happens, can you post VIm/Neovim,...
I'm not sure we always want paren mode for pasting. Paren mode would fail outright if the pasted code doesn't have balanced parens. I had an idea for separate plugin...