EMACS enviroment variable wrong in M-x compile

EMACS enviroment variable wrong in M-x compile

[David Kågedal]

In GNU Emacs 21.2.1 (i386-debian-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-03-22 on raven, modified by Debian
configured using `configure  i386-debian-linux-gnu --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --with-x=yes --with-x-toolkit=athena --without-gif'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: sv_SE.ISO8859-1
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: C
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

In Emacs 21.2 (from debian package emacs21 21.2-1), a change in
compile.el was introduced (but not mentioned in NEWS of even the
changelog) so that it doesn't set EMACS in the environment when
running compilation processes.  Unfortunately, the test seems to be
inverted.

compile.el:844:
	      (if (getenv "EMACS")
		  (setq process-environment
			(cons "EMACS=t" process-environment)))

Shouldn't the test be (not (getenv "EMACS"))?  As it is now, $EMACS
won't get set for me.


-- 
David Kågedal

Re: EMACS enviroment variable wrong in M-x compile

[Eli Zaretskii]

On Mon, 8 Apr 2002, David =?iso-8859-1?q?K=E5gedal?= wrote:

> In Emacs 21.2 (from debian package emacs21 21.2-1), a change in
> compile.el was introduced (but not mentioned in NEWS of even the
> changelog) so that it doesn't set EMACS in the environment when
> running compilation processes.  Unfortunately, the test seems to be
> inverted.
> 
> compile.el:844:
> 	      (if (getenv "EMACS")
> 		  (setq process-environment
> 			(cons "EMACS=t" process-environment)))
> 
> Shouldn't the test be (not (getenv "EMACS"))?  As it is now, $EMACS
> won't get set for me.

Thank you for your report.  Yes, this is a bug.  It will be fixed in the 
next release.