Path: utzoo!mnetor!uunet!husc6!think!ames!pasteur!ucbvax!YALE.ARPA!firby-james
From: firby-james@YALE.ARPA (James Firby)
Newsgroups: comp.sys.apollo
Subject: Prompt and EC2_WAIT
Message-ID: <8802220318.AA04482@ATHENA.CS.YALE.EDU>
Date: 22 Feb 88 03:18:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 53

Okay, I give up.  I've been trying every way I can think of to do the
following simple thing:  I want to print a prompt to an aegis shell
standard output (ie. IOS_$STDOUT) so that it shows up in the shell input
widnow and then WAIT until either a line is typed in, or a GPR event occurs.
I can't find any way to do this right.

Here is what I've tried:

Method 1:
  - write the prompt to IOS_$STDOUT
  - loop
    - check for input with IOS_$GET with [IOS_$COND_OPT, IOS_$PREVIEW_OPT]
    - check for GPR event
    - wait a little while
    - repeat

  The behavior of this is almost right except that every time the IOS_$GET
  is executed, the transcript pad is repositioned to the bottom (as if
  something had been written).  IOS_$GET does the right thing, returning
  nothing read, but the transcript behavior is unacceptable.

Method 2:
  - write the prompt to IOS_$STDOUT
  - read the IOS EVENTCOUNT and add 1 to its value
  - read the GPR EVENTCOUNT and add 1 to its value
  - block using EC2_$WAIT

  The behavior of this is correct except that the prompt never appears in
  the shell input window.

Method 3:
  - write the prompt to IOS_$STDOUT
  - do an IOS_$GET with [IOS_$COND_OPT, IOS_$PREVIEW_OPT]
  - read the IOS EVENTCOUNT and add 1 to its value
  - read the GPR EVENTCOUNT and add 1 to its value
  - block using EC2_$WAIT

  The behavior of this is correct except now the prompt pops up in the
  transcript pad on a line of its own when the IOS_$GET is executed.

This just shouldn't be this hard.  My current feeling is that there is
a bug in IOS_$GET using [IOS_$COND_OPT].  It just shouldn't have any
effect on the input or transcript pads but it does.

Can anyone help me with this?

Thanks.

Jim

PS - I am using AEGIS 9.7 (the same problem occured with 9.6).

-------