[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all cont
From: |
Eli Zaretskii |
Subject: |
bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents |
Date: |
Mon, 02 Nov 2020 20:35:57 +0200 |
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: lin.sun@zoom.us, larsi@gnus.org, sunlin7@yahoo.com,
> 44320@debbugs.gnu.org
> Date: Mon, 02 Nov 2020 19:22:21 +0100
>
> On Nov 02 2020, Eli Zaretskii wrote:
>
> > But that means 'fwrite' could return zero, if its very first call to
> > 'write' got interrupted, no?
>
> No. When an error occurs, it returns EOF.
Is EINTR considered an error for this purpose? If not, what exactly
is considered an error? I don't see this clearly documented, so it
could be something we cannot rely on. In fact, I don't even see in
portable documentation that it will return EOF upon errors, I only see
that the error indication for the stream shall be set and errno shall
be set.
In short, it sounds like calling fwrite in a loop will only work by
sheer luck.
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, (continued)
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents,
Eli Zaretskii <=
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, LinSun, 2020/11/02
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/03
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, LinSun, 2020/11/04
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/07
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, LinSun, 2020/11/08
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Eli Zaretskii, 2020/11/05
- bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send all contents, Andreas Schwab, 2020/11/05