On 2010-12-23 04:17 +0100, Petr Salinger wrote: >>> It seems that current plain FreeBSD kernel generates events >>> that fully corresponds to cons25 entry. >>> >>> It just uses different definitions for kbs and kdch1 wrt Linux, >>> >>> Linux: kbs=\177 kdch1=\E[3~ >>> FreeBSD/cons25 kbs=^H kdch1=\177 > >> >> Emacs, for instance, does not expect ^H to mean "delete previous >> character" by default. Instead it invokes the online help, which is >> annoying to no end. While this can be changed in .emacs, the backspace >> key not working out of the box is still a serious problem IMO. >> >>> It seems that upstream FreeBSD plans to switch their $TERM into xterm, >>> via TEKEN_XTERM. >> >> Actually the switch to xterm has happened already, more than one year >> ago: http://svn.freebsd.org/viewvc/base?view=revision&revision=199250. >> >> Note that Debian uses kbs=\177 in the xterm terminfo entry, while xterm >> upstream has kbs=^H. > > Given that, it might be the best way to really alter cons25 entry in > ncurses package (debian only) to use "kbs=\177 kdch1=\E[3~".
I don't see how this follows. People having an xterm-like terminal that is not compatible with Debian's xterm terminfo entry can easily work around it by setting TERM=xterm-r6 or similar when they connect to a Debian machine. What are FreeBSD users going to do when we introduce an incompatible cons25 entry? And what should GNU/kFreeBSD users do when they connect to a non-Debian machine? Sven -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mxnwfp1n....@turtle.gmx.de
