Re: connection_options() inconsistency

• Date: Thu, 9 May 1996 19:36:47 PDT
• From:
  David Morris <bweaver@worf.netins.net>
• Content-Type: text/plain; charset="us-ascii"

At 09:22 PM 5/9/96 -0500, phantom wrote:
>[just freshly connected to my character]
>;connection_options(player)
>=> {{"binary", 0}, {"flush-command", ".flush"}, {"hold-input", 0},
>{"client-echo", 0}}
>;set_connection_option(player, "client-echo", 0)
>=> 0
>
>I don't understand that.
> [snip]
>
>Shouldn't the client-echo connection option be 1 by default?
>

No, read the changelog (1.7.9alpha1) and the latest manual...

"client-echo" -- (NP_TCP configurations only) sends the Telnet protocol
     WON'T ECHO or WILL ECHO commands (depending on whether VALUE is
     true or false, respectively)...

So 1 means WON'T ECHO and 0 means WILL ECHO
--
David Morris
Green Mountain, Iowa
bweaver@worf.netins.net
http://www.netins.net/showcase/dmorris
or for the archives of Nerdnosh, the Story Digest...
http://www.netins.net/showcase/nerdnosh

• Prev: connection_options() inconsistency
• Next: Re: connection_options() inconsistency
• Index: MOO-cows
• Thread: MOO-cows