Subject: No echo?

From: [email-masked] (Michael J. Fromberger)
Date: Fri, 18 Jun 1993 11:57:09 -0700

Is it possible (and if so, how) to call read() such that the user's input is
not echoed on the terminal?  Can you send Telnet or ANSI sequences to this
effect from the MOO?

Please reply to me directly, as I am not on this list (yet).

:)

-Caedmon
(developing at aurora.dartmouth.edu, port 7777)

--
Michael J. Fromberger
Consultant, Postmaster
[email-masked] / [email-masked]

---

From: Peter <[email-masked]>
Date: Fri, 18 Jun 1993 13:03:56 -0700

Heh.  I did this with a pretty simple patch to the server, but I warn you
that there are a ton of problems with a non-echoing read.

The first is, if you want to do a prompt (I added a non-<CR>-ing tell as
well), here's what happens:

>Enter something:

Now, if you're just telneting to the MOO, you would then type your text,
and that's what the non-echoing read would get.  But, if you are using the
client, you will get the whole line returned (because the Emacs client
returns everything between the '>' and the linefeed).  Lame.  But it can
be filtered out (sort of) by just scanning through the returned string and
removing '>Enter something: ' from the beginning, if indeed it exists.
Clear?  No?  Hm.

Also, if you want to do an LP-style login:/password: deal, forget it.  If
you try to do a read() of any sort in do_login_command, do_login_command
will NEVER return a value.  I don't really know why, but I do know that
read() is a bit of a hack anyway.

So, if that didn't discourage you, I'd be glad to mail you the server mods
(they're pretty trivial).

                       [gcc]                                     [g++]
/*--------------------------            // ---------------------------
  Peter (Z-man) Zatloukal               //  Peter (Z-man) Zatloukal
  NeXT Lab Administrator                //  ACC Lead Lab Assistant
  [email-masked]             //  [email-masked]
  --------------------------*/          // ---------------------------