[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking
From: |
Brand Huntsman |
Subject: |
[Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking on it |
Date: |
Mon, 13 May 2019 23:59:18 -0600 |
The open() in open_file() blocks if an empty FIFO is opened, causing nano to
hang. This patch opens the FIFO in non-blocking mode, polls it for data and
re-opens it in blocking mode if data found. Just start the writing process
first, and then open nano.
It would also be nice if a "Writing to FIFO..." message was displayed before
writing to one. It would provide a little feedback as to why nano hangs if the
FIFO is no longer listening.
files-check-for-an-empty-FIFO-before-blocking-on-it.patch
Description: Text Data
- [Nano-devel] [PATCH 1/2] files: allow a given file to be a special file but not a directory, Benno Schulenberg, 2019/05/12
- [Nano-devel] [PATCH 2/2] files: check for writability by the access bits, not by trying to append, Benno Schulenberg, 2019/05/12
- [Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking on it,
Brand Huntsman <=
- Re: [Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking on it, Benno Schulenberg, 2019/05/15
- Re: [Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking on it, Brand Huntsman, 2019/05/15
- Re: [Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking on it, Benno Schulenberg, 2019/05/16
- Re: [Nano-devel] [PATCH 3/3] files: check for an empty FIFO before blocking on it, Brand Huntsman, 2019/05/17
- [Nano-devel] interrupting an open() does not work with gcc, Benno Schulenberg, 2019/05/23
- Re: [Nano-devel] interrupting an open() does not work with gcc, Benno Schulenberg, 2019/05/23
- Re: [Nano-devel] interrupting an open() does not work with gcc, Brand Huntsman, 2019/05/23
- Re: [Nano-devel] interrupting an open() does work with gcc when flags are zeroed, Benno Schulenberg, 2019/05/23