Usage:
/LOCALECHO [ON|OFF]
/Localecho with no arguments returns 1 if local echoing is enabled for the current socket, 0 otherwise. TF echoes its input by default, unless the server has negotiated otherwise.
/Localecho with an argument attempts to enable or disable echoing for the current socket. If the server is not known to support TELNET protocol, "/localecho [ON|OFF]" does nothing, and returns 0. ON tells the server DONT ECHO; if the server acknowledges (as it must according to TELNET protocol), tf will echo its own input. OFF tells the server to DO ECHO; if the server acknowledges, tf will not echo its own input, expecting the server to do it. The actual change of state takes place after the server agrees, which may be delayed by network latency ("netlag").
Note that tf does not transmit input until a newline is pressed, and the server can not echo it until it is received; so, with /localecho off, your typing will not be visible until you hit return, at which time the server may echo back the entire line.
Some mud servers use the ECHO option to disable local echo during password entry. Telnet servers, however, try to disable local echo for the entire session, which would interfere with many useful tf features. Hooks defined in the standard library use /localecho to override the telnet server automatically.
/Localecho is intended to be called by library macros, and should not need to be called by the user. /Localecho obsoletes %{always_echo}.
The TELNET ECHO option is defined in RFC 857.
See: prompts, %telopt, /telnet