[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/51556: less(1) generates SIGTTOU if lacking a controlling terminal
The following reply was made to PR bin/51556; it has been noted by GNATS.
From: Thomas Klausner <wiz%NetBSD.org@localhost>
Subject: Re: bin/51556: less(1) generates SIGTTOU if lacking a controlling
Date: Thu, 13 Oct 2016 06:47:59 +0200
On Thu, Oct 13, 2016 at 04:20:00AM +0000, Matthew Green wrote:
> i'm convinced there are two bugs here. the timeout one, and
> that less tries to do terminal ops that trigger signals when
> not properly able.
> the original report fails if you use 'cat' instead of 'less'.
> i'd not be so worried about the less bug, but for me i can't
> ^C out of it. ^Z does work, but having a shell i can't sent
> an interrupt to is pretty serious situation i'd like to avoid
> having happen if the tools can.
I'm not sure this is related, but a bug I've been seeing for a couple
of releases now reminds me of that.
start mutt (mail/mutt or mail/neomutt)
type '|less' to pipe a mail through less
interrupt with CTRL-Z
continue with fg
at this point, the screen is not updated, neither by less nor mutt and it seems neither is in control of the terminal
interrupt again with CTRL-Z
continue again with fg
at this point we're back in less and everything works as if nothing
Main Index |
Thread Index |