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

Previous Next

To reply to this bug, email your comments to 5331 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

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

From: Scott Bell <sctb <at> me.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Term mode doesn't set tty erase
Date: Wed, 06 Jan 2010 16:54:28 -0700

Under Mac OS X 10.6.2, Emacs 23.1.90.1, in an M-x term buffer
running /bin/bash, `stty -a' reports the following:

speed 9600 baud; 33 rows; 90 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
        -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
        -extproc
iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -iutf8
        -ignbrk brkint -inpck -ignpar -parmrk
oflags: opost onlcr -oxtabs -onocr -onlret
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow
        -dtrflow -mdmbuf
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
        eol2 = <undef>; erase = <undef>; intr = ^C; kill = <undef>;
        lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q;
        status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W;

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.

Message #8 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: Thu, 7 Jan 2010 00:27:37 -0800 (PST)

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

  > Under Mac OS X 10.6.2, Emacs 23.1.90.1, in an M-x term buffer
  > running /bin/bash, `stty -a' reports the following:
  > 
  > speed 9600 baud; 33 rows; 90 columns;
  > lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
  >         -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
  >         -extproc
  > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -iutf8
  >         -ignbrk brkint -inpck -ignpar -parmrk
  > oflags: opost onlcr -oxtabs -onocr -onlret
  > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow
  >         -dtrflow -mdmbuf
  > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
  >         eol2 = <undef>; erase = <undef>; intr = ^C; kill = <undef>;
  >         lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q;
  >         status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W;
  > 
  > 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?

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

From: Scott Bell <sctb <at> me.com>
To: 5331 <at> debbugs.gnu.org
Subject: Re: bug#5331: Term mode doesn't set tty erase
Date: Thu, 07 Jan 2010 09:14:29 -0700

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 ^?.

Message #14 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: Thu, 7 Jan 2010 13:35:20 -0800 (PST)

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.

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

From: Scott Bell <sctb <at> me.com>
To: 5331 <at> debbugs.gnu.org
Subject: Re: bug#5331: Term mode doesn't set tty erase
Date: Fri, 08 Jan 2010 10:06:54 -0700

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.

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.

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

From: Scott Bell <sctb <at> me.com>
To: 5331 <at> debbugs.gnu.org
Subject: Re: bug#5331: Term mode doesn't set tty erase
Date: Fri, 08 Jan 2010 12:23:12 -0700

On 2010-01-08, at 12:09 PM, Dan Nicolaescu wrote:

> 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:
>>> 
>>> 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.

Terminal.app has to be doing something, because I've tried
setting term-term-name to 'xterm-color', which is the same
TERM used by Terminal.app. So it seems like buggy shell
initialization which Terminal.app is overriding somehow.

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

From: Andrew Hyatt <ahyatt <at> gmail.com>
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: Wed, 03 Aug 2016 21:50:36 -0400

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

> On 2010-01-08, at 12:09 PM, Dan Nicolaescu wrote:
>
>> 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:
>>>> 
>>>> 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.
>
> Terminal.app has to be doing something, because I've tried
> setting term-term-name to 'xterm-color', which is the same
> TERM used by Terminal.app. So it seems like buggy shell
> initialization which Terminal.app is overriding somehow.

This bug reproduces on Emacs 25.1.50.1. I also tried running emacs via
iTerm2 and it had the same issue.

Previous Next

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