GNU bug report logs - #44320
[PATH] [27.1] Make sure send-string-to-terminal send all contents

Previous Next

Full log

Message #86 received at 44320 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: larsi <at> gnus.org, sunlin7 <at> yahoo.com, 44320 <at> debbugs.gnu.org, lin.sun <at> zoom.us
Subject: Re: bug#44320: [PATH] [27.1] Make sure send-string-to-terminal send
 all contents
Date: Thu, 05 Nov 2020 17:59:26 +0200

> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Cc: lin.sun <at> zoom.us,  larsi <at> gnus.org,  sunlin7 <at> yahoo.com,
>   44320 <at> debbugs.gnu.org
> Date: Mon, 02 Nov 2020 21:26:18 +0100
> 
> On Nov 02 2020, Eli Zaretskii wrote:
> 
> > Too many subtle assumptions for my palate.  In general, stdio is not
> > safe in the presence of signals.
> 
> That is true, at least if the stream is conntected to a blocking device
> (file I/O is not affected by signals).

So you are saying only console and PTY I/O needs this special
handling, and file I/O doesn't?

> > Would it be better to suspend SIGIO by calling unrequest_sigio instead
> > (and resume it once 'fwrite' returns)?
> 
> It might be even better to use POSIX I/O.

Maybe so, but that sounds like a too large change for such a rare and
subtle use case.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.