On Fri, Jun 17, 2005 at 02:29:32PM -0400, Frédéric Brière wrote: > On Fri, Jun 17, 2005 at 02:17:19PM -0400, Thomas Dickey wrote: > > Perhaps because $TERM is set to "xterm" rather than "Eterm". > > Guilty as charged. TERM=Eterm was a PITA when ssh'ing into old boxen > that didn't recognize it, so I got rid of it a long time ago. > > I confirm that TERM=Eterm makes everything dandy again. (Plus, these > old boxen appear to have been upgraded, so I can get rid of that xterm > kludge.) > > Given that Eterm aims to be xterm-compatible, does this mean this bug > report should be reassigned to it?
Up to you: either it's a bug in eterm or in your terminal settings. The two really aren't compatible; "infocmp Eterm xterm" to see the differences. -- Daniel Jacobowitz CodeSourcery, LLC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
