Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ulysses!ucbvax!info-vax
From: powers@TESLA.EE.CORNELL.EDU (Garry Wiegand)
Newsgroups: mod.computers.vax
Subject: Re: clearing recall-buffer
Message-ID: <8511180042.AA27271@tesla.ee.cornell.edu>
Date: Sun, 17-Nov-85 19:42:07 EST
Article-I.D.: tesla.8511180042.AA27271
Posted: Sun Nov 17 19:42:07 1985
Date-Received: Tue, 19-Nov-85 04:04:13 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: garry%geology@cu-arpa.cornell.edu.arpa
Organization: Cornell Engineering && Flying Moose Graphics
Lines: 24
Approved: info-vax@sri-kl.arpa

In article <...> S211KENO@HTIKHT5.BITNET writes:
>Of course I do set terminal/noecho before the INQUIRE-statement, but
>onfortunately the password is still in the recall-buffer.
>
>Does anybody know how to clear the recall-buffer ?

It appears the DCL routines which extend the terminal driver's memory 
don't agree with the terminal driver itself about whether to save non-echoed 
input. The driver's probably right since you're not very likely to be 
editing a command you can't see...

To do it the driver's way, use Read rather than Inquire:

          $ read/prompt="Password: " sys$command password

I think this should solve your problem.

(An explicit Read to the terminal is more often used when you want the
input precisely as typed (no conversion to upper case...), or when
a /TIME_OUT would be a good thing.)


Garry Wiegand
garry%geology@cu-arpa.cs.cornell.edu  (arpa)