[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why does "mapfile -d delim" (delim != '\n') use unbuffered read?

From: Andreas Schwab
Subject: Re: Why does "mapfile -d delim" (delim != '\n') use unbuffered read?
Date: Tue, 04 May 2021 15:03:10 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

On Mai 04 2021, Chet Ramey wrote:

> On 5/4/21 3:26 AM, Andreas Schwab wrote:
>> On Mai 03 2021, Chet Ramey wrote:
>>> It won't work on any system that doesn't return -1/ESPIPE when you try
>>> to lseek on a terminal device. Glibc does;
>> Glibc doesn't do anything, it just uses what the kernel says.
> You'd think, but the manual says otherwise about ESPIPE:
> "The filedes corresponds to an object that cannot be positioned, such as a
> pipe, FIFO or terminal device. (POSIX.1 specifies this error only for pipes
> and FIFOs, but on GNU systems, you always get ESPIPE if the object is not
> seekable.)"

How does that contradict what I said?


Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]