Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: (more) Re: PATCH: 3.1.5* & 3.0.5: Re: strange xterm & zsh behaviour
- X-seq: zsh-workers 5125
- From: Drazen Kacar <dave@xxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: PATCH: (more) Re: PATCH: 3.1.5* & 3.0.5: Re: strange xterm & zsh behaviour
- Date: Sat, 30 Jan 1999 19:27:46 +0100
- Cc: Drazen Kacar <dave@xxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: <990130100451.ZM12586@xxxxxxxxxxxxxxxxxxxxxxx>; from Bart Schaefer on Sat, Jan 30, 1999 at 10:04:51AM -0800
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <9901301251.AA43826@xxxxxxxxxxxxxxxxx> <990130100451.ZM12586@xxxxxxxxxxxxxxxxxxxxxxx>
Bart Schaefer wrote:
> (For Drazen) Is it desirable to ALWAYS do this? For a backgrounded shell,
> calling ioctl() on a tty device will usually result in a SIGTTOU stopping
> the process.
Just for the first interactive shell on the terminal. Background shell
doesn't fall in that category. But why should a background shell attempt
to initialize the terminal? It seems to me that background shell shouldn't
call that function. On a related matter, does subshell initialize terminal?
> (For PWS et al.) Even if it should always be done, I think it'd be a good
> idea to move this code down the point where an attempt to open /dev/tty
> might be made anyway, so that it needn't be opened and closed more than
> once.
I thought it was at that point, but diff didn't provide enough context and
I'm without sources.
--
.-. .-. Life is a sexually transmitted disease.
(_ \ / _)
| dave@xxxxxxx
| dave@xxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author