Per puzzles:

[snip]

>I just had to try this, and would be really interested if someone could
>explain why the CI changes behaviour whith the change of the HPPROMPT
>variable, if what is shown below is related to John's original question,
>and, if this is to be considered a bug or a feature (:-):
>
>-<'test;-)-result', my input (afterwards) enclosed in '"',comments in '<>'>-
>
>:"hello mgr.kemtest"
>CPU=1. Connect=3. TUE, JUL  8, 1997,  9:50 AM.
>ENTER ACCOUNT (KEMTEST) PASSWORD:
>
>HP3000  Release: C.50.00   User Version: C.50.00   TUE, JUL  8, 1997,  9:50
>AM
>MPE/iX  HP31900 B.79.06  Copyright Hewlett-Packard 1987.  All rights
>reserved.
>:":"
>:       <nothing happens>
>:"setvar hpprompt hpuser"
>MGR":"
>Invalid first character in command name. (CIERR 9090)
>        <so now I get CIERR 9090>
>MGR"MGR"
>MGR     <hmm.. nothing again, this is really related to the prompt>
>MGR"setvar hpprompt 'SHOWME'"
>SHOWME"SHOWME"
>SHOWME  <so now I can't do a showme!!>
>SHOWME"showme"
>USER: #S11061,MGR.KEMTEST,PUB      (NOT IN BREAK)
>RELEASE: C.50.00   MPE/iX HP31900 B.79.06   USER VERSION: C.50.00
>CURRENT: TUE, JUL  8, 1997,  9:57 AM
>LOGON:   TUE, JUL  8, 1997,  9:50 AM
>CPU SECONDS: 0         CONNECT MINUTES: 7
>$STDIN LDEV: 197         $STDLIST LDEV: 197
>SHOWME   <at least it's case sensitive>
>-<end>-

This behavior exists for mpe 4.0 as well as 5.5. Evidently the input
must be exact - appending a ' ' (space) or not matching the case exactly
will execute the command.

I believe this behavior is designed into the ci such that beginning
text of any transmitted command that matches the existing prompt is
removed from the command input.

This is a feature that allows you to use the <enter> key to transmit
a line from your screen that has a prompt followed by a command
and have the command be executed without having to remove the prompt.
This is a handy feature that I use quite often.

Note: <enter> is the block mode <enter>, not a <cr> masquerading as
      the <enter> key on a pc keyboard.

Warning: If you haven't used this feature, be careful in duplicating
         these examples. Do *not* type the command followed by <enter>
         or you will get two commands (showjobshowjob) because the first
         'showjob' is already in the ci input buffer. These examples are
         of the text being on the screen and moving the cursor to the
         line and pressing <enter>. Assuming the input buffer is empty
         you will have tranmitted the line as if you had typed it in.

For example (with a prompt of 'showme'):

showmeshowjob<enter>

Causes a showjob command to be executed, even though 'showmeshowjob' was
transmitted. To check it out, do a 'redo' and you'll see that the redo
buffer is 'showjob', the ci having stripped off the 'showme'.

You can see this behavior as well by just pressing the <enter> key at
the ci prompt:

showme<enter>

Even though 'showme' was transmitted, you get another prompt as if the
<cr> had been pressed.



Duane Percox ([log in to unmask]  v/415.306.1608 f/415.365.2706)
http://www.qss.com/          http://qwebs.qss.com/qwebs
http://qwebs.qss.com/faq3k