Xref: utzoo comp.unix.admin:524 comp.unix.questions:26901 comp.unix.shell:895
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.admin,comp.unix.questions,comp.unix.shell
Subject: Re: telnet in a shell script
Message-ID: <16864:Nov1421:49:3890@kramden.acf.nyu.edu>
Date: 14 Nov 90 21:49:38 GMT
References: <8026@muffin.cme.nist.gov> <7006:Nov1408:13:3290@kramden.acf.nyu.edu> <8028@muffin.cme.nist.gov>
Organization: IR
Lines: 16

In article <8028@muffin.cme.nist.gov> libes@cme.nist.gov (Don Libes) writes:
> expect does understand job control.

No, it does not.

When I type ``z'' to telnet or ``suspend'' to csh, I expect it to stop.
The interaction should be transparent; the user shouldn't have to think
about expect being in the way. But expect doesn't monitor the status of
the spawned process and hence cannot handle job control transparently.
This is a limitation and you know it.

> (The man page explains all this.)

Yes, it does.

---Dan