GNU bug report logs - #5331
Term mode doesn't set tty erase

Previous Next

Full log

Message #22 received at 5331 <at> debbugs.gnu.org (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Scott Bell <sctb <at> me.com>
Cc: 5331 <at> debbugs.gnu.org
Subject: Re: bug#5331: Term mode doesn't set tty erase
Date: Fri, 8 Jan 2010 11:09:14 -0800 (PST)

Scott Bell <sctb <at> me.com> writes:

  > On 2010-01-07, at 2:35 PM, Dan Nicolaescu wrote:
  > 
  > > Scott Bell <sctb <at> me.com> writes:
  > > 
  > >> On 2010-01-07, at 1:27 AM, Dan Nicolaescu wrote:
  > >> 
  > >>> Scott Bell <sctb <at> me.com> writes:
  > >>> 
  > >>>> ...
  > >>>> 
  > >>>> It seems like the least surprising thing would be to define
  > >>>> erase to ^? so that most programs will behave as expected 
  > >>>> when the DEL key is typed.
  > >>> 
  > >>> I can't reproduce this on GNU/Linux and Solaris.
  > >>> This is probably a Mac OS X problem which not too many people here have
  > >>> access to...
  > >>> Do you get the same results with /bin/tcsh?
  > >> 
  > >> It looks like tcsh is the only one where erase
  > >> is defined:
  > >> 
  > >> bash: <undef>
  > >> zsh: <undef>
  > >> tcsh: ^?
  > >> ksh: <undef>
  > >> 
  > >> When these shells are launched using Terminal.app
  > >> (the terminal emulator that ships with Mac OS), erase
  > >> is always bound to ^?.
  > > 
  > > term.el does not do anything special for tcsh, so because it works
  > > there, it's probably a problem in the initialization of the other
  > > shells, not in term.el.
  > 
  > I agree. It seems like a shame that Mac OS relies on
  > the default emulator (Terminal.app) to perform this
  > initialization.

Not sure what you mean...
It's probably due to buggy initialization for those shells, or because
they get confused about TERM value used by term.el: eterm-color.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.