HP3000-L Archives

December 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Gale <[log in to unmask]>
Reply To:
David Gale <[log in to unmask]>
Date:
Fri, 3 Dec 1999 07:23:28 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Jeff,

I vote fot placing this on the INPUT command. Tom makes a good point about
the PAUSE command, but as the input command already has a timeout parameter
as well as other features, I like the idea.

Also, perhaps HP shouldn't limit themselves to the console. Maybe any
terminal device or class. That way it could fit into more environments.

Not awake yet.

Dave

-----Original Message-----
From: VANCE,JEFF (HP-Cupertino,ex1) [mailto:[log in to unmask]]
Sent: Thursday, December 02, 1999 4:34 PM
To: [log in to unmask]
Subject: Re: Brain Took a Vacation


Hi all,

While this topic is fresh, does anyone care to propose a
syntax for a new CI command, or an extension to the INPUT
command (and/or input function) or a new CI function??

Is it worth having a built-in 'repeater' ability, so the request
is repeated at the console.  Should there be a timeout?  Should
there be some basic cursor control/memory lock ability? etc..

regards,
Jeff Vance, CSY

> What is the command or option that will pause a job until
> there is a reply from the operator. Would like it to operate
> like the INPUT command.

ATOM RSS1 RSS2