Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!jsq From: sef@kithrup.COM (Sean Eric Fagan) Newsgroups: comp.std.unix Subject: Re: disabling TIOCGPGRP on pty master sides Message-ID: <16306@cs.utexas.edu> Date: 29 Dec 90 04:25:11 GMT References: <16068@cs.utexas.edu> <16118@cs.utexas.edu> <16290@cs.utexas.edu> Sender: jsq@cs.utexas.edu Organization: Kithrup Enterprises, Ltd. Lines: 41 Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman) X-Submissions: std-unix@uunet.uu.net Submitted-by: sef@kithrup.COM (Sean Eric Fagan) In article <16290@cs.utexas.edu> thorinn@diku.dk (Lars Henrik Mathiesen) writes: >By the way, I will hazard a guess: Most, if not all, of the UNIX >variants where the existing practice of Emacs doesn't work will have >SYSV termios ioctls. Yep. All POSIX systems. >So instead of putting in ifdefs for two or three >subtly incompatible new TIOCSENDSIGs, we might as well put in the four >lines to get a termios structure and stuff the appropriate character >down the master pty. (shell) kithrup 341> stty intr ^Y kithrup 342> ^?^?^?^? Gosh. It doesn't seem to be sending the control-y to the slave side of the pty! And, gosh, if it tries to do a TCGETAW, it just hangs! (Actually, I think it gets a SIGTTIN.) Some of this is SCO specific. But without rewriting the pty driver, *any* POSIX system with ptys is going to have the same problem (since sco's pty drivers aren't that different from berkeley's). According to email I exchanged with someone at CSRG, 4.4 will support the old method, but as an obsolescent feature. If the text is so ambiguous that it is implemented differently on every system, that means that you will need more ifdef's than with just the TIOCSIG ioctl. -- Sean Eric Fagan | "I made the universe, but please don't blame me for it; sef@kithrup.COM | I had a bellyache at the time." -----------------+ -- The Turtle (Stephen King, _It_) Any opinions expressed are my own, and generally unpopular with others. Volume-Number: Volume 22, Number 46