Open theindexer opened 4 years ago
Thanks for reporting! I haven't run into it yet but the pointers are wonderful to have tracked for when it does start causing problems in practice.
I just notice the referenced vim bug was closed in 2018. Was it not completely fixed, or just still out there on older vim versions?
Specifically on Linux, if I send more than 4097 bytes to stdin I get ch_sendraw(): write failed If the command produces output, then vim hangs indefinitely, before even displaying the ch_sendraw error.
This looks suspiciously like https://github.com/vim/vim/issues/2548
Tried to patch it with https://github.com/natebosch/vim-lsc/issues/67#issuecomment-357469091
but I don't actually know what I'm doing in vimscript and just ended up with some channel closed errors after the first chunk. Also I could be barking up the wrong tree.
For me personally, I'm no longer using stdin so I'm no longer affected by this but still seems like a bug?