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 5123
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Drazen Kacar <dave@xxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: PATCH: (more) Re: PATCH: 3.1.5* & 3.0.5: Re: strange xterm & zsh behaviour
- Date: Sat, 30 Jan 1999 10:04:51 -0800
- In-reply-to: <9901301251.AA43826@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <9901301251.AA43826@xxxxxxxxxxxxxxxxx>
On Jan 30, 1:51pm, Peter Stephenson wrote:
} Subject: Re: PATCH: (more) Re: PATCH: 3.1.5* & 3.0.5: Re: strange xterm &
}
} Peter Stephenson wrote:
} > You mean something like the following? I don't quite know how to test
} > for this, since you can't be assured fd 0 is /dev/tty. Maybe the
} > ioctl() on its own is enough.
}
} sorrysorry... this time I've tested it. (I didn't realise I could on
} AIX, but TIOCNXCL does exist after all.) This replaces the one two
} minutes ago.
Misc. remarks:
(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.
(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.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author