Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!chinet!sid
From: sid@chinet.UUCP (Sid Grange)
Newsgroups: comp.emacs
Subject: Re: How do I get pty's to work in GNU emacs?
Message-ID: <1631@chinet.UUCP>
Date: Sat, 26-Sep-87 20:05:39 EDT
Article-I.D.: chinet.1631
Posted: Sat Sep 26 20:05:39 1987
Date-Received: Sun, 27-Sep-87 11:45:09 EDT
References: <1821585@ncrcpx.UUCP>
Reply-To: sid@chinet.UUCP (Sid Grange)
Distribution: na
Organization: Chinet - Public Access Unix
Lines: 25
Keywords: pty sysv emacs
Summary: Hmm.. Worked for me.

In article <1821585@ncrcpx.UUCP> craig@ncrcpx.UUCP (R. Craig Peterson) writes:
>
>I'm running GNU Emacs 18.47 on a SYSVR2 machine.  I've installed the
>pty driver that was on the net into my os, and have put the HAVE_PTYS,
>and the FIRST_PTY_LETTER defines into my include file.
>
>I'm able to compile emacs just fine, however when I spawn off a shell
>(w/M-x shell) it doesn't use a pty.  The same is true when I try and
>use the shell-command function.

 I had the very same problem with version 18.37 (yes, I should have the
new version) on my 3b1 (running 3.51). I would run a shell and it would
dogmatically use a pipe. I went back and checked things. I'd simply
made a pretty dumb mistake (I switched from m-usg5-2.h to s-usg5-2-2.h
and made my pty define in there. But I FORGOT to change config.h to reflect
the intended change in include files. Needless to say, it compiled with
the old include file. After I fixed config.h the pty's worked flawlessly.
Are you sure you didn't make a dumb mistake like me? :-) What kind of
machine are you running it on specifically? The lisp variable 
process-connection-type must be set to t if emacs is to use a pty. If it
is nil a pipe will be used. Your emacs should default to t, I believe.
--
	Sid Grange
	sid@chinet
	ihnp4!chinet!sid