[MUD-Dev] handling ambiguity, and prompts

[Chris Gray]

[Raz:]
:From my position as a designer, it seems to me that any command issued
:immediately after a question prompt would be assumed to be a response to =
:the
:question - if the response fails to satisfy the requirements of the =
:prompt,
:then the prompt is cancelled and the 'response' is handled as the regular
:command that it is.

I could probably handle that, but I would still like a way to turn off any
such prompting. If you have an RL interruption, or even an in-MUD one,
the command and prompt can disappear off your screen and out of your
memory. If the prompt itself is always visible, and indicates that a
question is pending, then you should be able to enter something that
will specifically cancel *any* outstanding question.

In earlier discussions, Chris L. had talked about nested questions/prompts,
and ways of suspending them indefinitely using an escape character to allow
you to force through a non-answering command without cancelling the
question/prompt. This kind of thing is what would bother me as a user -
the "stack" in my brain is only about 2 deep!

--
Chris Gray   cg at ami-cg.GraySage.Edmonton.AB.CA