Let's simulate a read that will block forever:
$ mkfifo /tmp/myfifo
$ vim /tmp/myfifo
Now vim hangs permanently; it cannot be killed or suspended except by
going to another terminal and running `pkill -9 vim`. (Or, of course,
writing stuff to the fifo, but the point here wasn't about fifos
specifically, but just about reads that are slow to return for whatever
reason).
Same story with :w or :w! to a file that is slow to write.
IMO, this "hang forever and give the user no way to recover" behavior is
a bug, but reasonable people might disagree.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/1336a982-cbde-bdf8-0db0-89d39218750f%40umanwizard.com.
