There's not much info about the exact number of devices. After a bit of searching I've found posts in various forums from 2003-2010 with similar (but not exact) backspace/new line issues. I guess some of the ancient devices don't support backspace - mostly devices with some proprietary OS or strange terminal implementation.
The thing is, these IAC's should be generic as stated in telnet's RFC: > Just as the NVT data byte 68 (104 octal) should be mapped into > whatever the local code for "uppercase D" is, so the EC character > should be mapped into whatever the local "Erase Character" > function is. And from what I've seen from a couple of telnet servers (busybox excluded), they support it. On Fri, 18 Oct 2019 at 09:47, Denys Vlasenko <[email protected]> wrote: > On Mon, Jul 8, 2019 at 4:38 PM Martin Lewis <[email protected]> > wrote: > > Closes https://bugs.busybox.net/show_bug.cgi?id=11976 > > > > Adds a new flag in telnet client's command line, which > > forces telnet to send IAC's instead of the > > traditional special characters (backspace, newline etc..). > > > > This code is similar to putty's code, and is added > > for compatibility with older telnet servers. > > I'm not applying it yet, waiting for more user reports - > how many devices are there which don't understand backspace/DEL chars? >
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
