Re:Vim's 400 line function to wait for keyboard input
by UberMouse on Wednesday July 15, 2015 @05:58PM
(#9894330)
I use Neovim as my daily editor, it definitely has it's quirks over Vim (sometimes it takes over 10 seconds to write to certain files, locking up Neovim and there are some bugs with the fuzzy finder I use that cause file corruption that aren't present in Vim) but on the whole it's pretty stable. Haven't encountered any issues yet that are more than a minor annoyance.
[ Parent
| on HN ]
Re:Vim's 400 line function to wait for keyboard input
by simoncion on Thursday July 16, 2015 @02:35AM
(#9895731)
> ...there are some bugs with the fuzzy finder I use that cause file corruption...
Having your text editor corrupt the file it's working on sounds like the absolute worst case scenario.
Is this fuzzy finder thing some third-party plugin? Do you have any idea why it corrupts the files that you point it at?
Re:Vim's 400 line function to wait for keyboard input
by UberMouse on Thursday July 16, 2015 @10:18PM
(#9901006)
It's a third party plugin, it's definitely a Neovim issue because the file corruption doesn't happen with Vim. No idea why it happens. I'm fine living with it because I just check the file back out if it corrupts it. It's only an issue when opening a new file so it doesn't cause work to be lost.
A github issue about it https://github.com/junegunn/fzf/issues/206