Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site t4test.UUCP
Path: utzoo!linus!decvax!decwrl!sun!idi!t4test!chip
From: chip@t4test.UUCP (Chip Rosenthal)
Newsgroups: net.eunice
Subject: Re: Spawning an interactive DCL from Eunice
Message-ID: <1238@t4test.UUCP>
Date: Wed, 14-Nov-84 05:33:24 EST
Article-I.D.: t4test.1238
Posted: Wed Nov 14 05:33:24 1984
Date-Received: Fri, 16-Nov-84 01:45:12 EST
References: <382@noao.UUCP> <590@sjuvax.UUCP> <1454@sdcrdcf.UUCP>
Organization: Intel Corp./Santa Clara
Lines: 24
Summary: ^Y while suspended

> From: lwall@sdcrdcf.UUCP (Larry Wall)
> Date: 9 Nov 84 19:02:59 GMT
> 
> Another limitation is that ^Y won't work.  Woe betide if you say "dir/full"
> in a directory with 1000 versions.  There's no way to stop it short of
> killing the process.

Not true.  When a shell is opened, ^Y is turned off.  The reason is
obvious...ugly things would happen if you did a ^Y in csh and VMS trapped
it.  If you do a "suspend", a simple

	SET CONTROL=Y

will enable ^Y for the duration of the DCL.  (Today's handy hint: define
"Y" as a logical name to do this).  Of course, if you don't enable ^Y you
can always ^O, drum your fingertips merrily on the tabletop for 30 seconds
or so, and then continue on when you get your prompt back.  As ugly as the
^O solution is, it's probably easier (and quicker) than logging on somewhere
else, locating your PID, and stopping it.

-- 

Chip Rosenthal, Intel/Santa Clara
{cbosgd,idi,intelca,icalqa,kremvax,qubix,ucscc} ! {t4test,t12tst} ! {chip,news}