GNU bug report logs - #20202
24.3; Comint mode sets a bad $EMACS

Previous Next

Package: emacs;

Reported by: Eli Barzilay <eli <at> barzilay.org>

Date: Wed, 25 Mar 2015 21:46:02 UTC

Severity: minor

Found in version 24.3

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


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

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 20202 <at> debbugs.gnu.org, 20484 <at> debbugs.gnu.org,
 Phillip Lord <phillip.lord <at> russet.org.uk>
Subject: Re: bug#20484: bug#20202: Considered Harmful 73d213: 'Comint, term,
 and compile new set Emacs'
Date: Thu, 07 Apr 2016 12:51:51 -0400
>> I can think of several possibilities. In particular, the EMACS=t behaviour
>> of bash should also be replicable with bash -o emacs.
> I expect that this problem affects programs other than bash.  For example,
> tcsh 6.19.00 (the latest version of the first other shell that I checked)
> tests whether EMACS is "t".

It's not clear to me what "affects" means here.
The problem explicitly reported in 20484 is that directory tracking is
"turned off".  This doesn't sound particularly terrible (as long as
there's an easy way to get back the desired directory tracking).

So I think to make an informed decision, we first need to figure out *how*
all those shells are affected by having $EMACS be set to something else
than "t".

Maybe the best solution is to stop messing with $EMACS by default (and
hence change the behavior of sub-shells in negative ways for some
users), and then provide an easy way for those users to get back the
"fully featured" sub-shell they love.


        Stefan




This bug report was last modified 7 years and 38 days ago.

Previous Next


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