Just too bad Debian's policy is to make ^? the erase character - pretty
much the opposite of what most Unix users used before that. Pretending
ASCII BS (^H) doesn't exist any more is an interesting exercise, but
it isn't easy to change habits and standards that existed for a couple of
decades... The same problem exists for the ASCII DEL (^?) which was also used
in many Unix systems, but usually as a intr key, not a "delete-forward" type
of thing...
[see http://www.debian.org/doc/debian-policy/ch-opersys.html#s10.8
for the mentioned Debian policy]
Debian's solution isn't a silver bullet, in my opinion... It just means the
^H/^? confusion stops being a problem in a stand-alone system (if all your
applications and configuration files come as defaults from Debian, they are
consistent) but it just increased the mess when you log in from one system
type to another (one of them being none-Linux Unix)...
P.S.
The only relation any of this has to the kernel is the behavior of the
"cooked" line discipline, as Zefram already said. I think I like his
erase2 idea better than his forget-the-difference-between-^H-and-^? idea.
However, this former idea will work well only if applications like ssh,
for example, will know how to propegate erase2, and they currently don't.
But this is again not really a kernel issue...
-- Nadav Har'El | Sunday, Sep 23 2001, 7 Tishri 5762 nyh@math.technion.ac.il |----------------------------------------- Phone: +972-53-245868, ICQ 13349191 |Experience is what causes a person to http://nadav.harel.org.il |make new mistakes instead of old ones. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/