GNU bug report logs - #30134
ehsell and process-environment variable

Previous Next

Package: emacs;

Reported by: SK Kim <tttuuu888 <at> gmail.com>

Date: Tue, 16 Jan 2018 02:32:01 UTC

Severity: minor

Tags: notabug

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: SK Kim <tttuuu888 <at> gmail.com>
Cc: 30134 <at> debbugs.gnu.org
Subject: Re: bug#30134: ehsell and process-environment variable
Date: Tue, 16 Jan 2018 05:40:33 +0200
> From: SK Kim <tttuuu888 <at> gmail.com>
> Date: Tue, 16 Jan 2018 11:31:27 +0900
> 
> 1) start emacs with 'emacs -Q'
> 
> 2) 'M-x eshell' to open eshell buffer.
> 
> 3) evaluate below code in eshell buffer.
>     (let ((process-environment (cons "TEST=1234" process-environment)))
>         (make-term "test-term" "/bin/bash"))
> 
> 4) moved to buffer 'test-term' and type 'echo $TEST' and you can see
>    nothing.
> 
> The modified process-environment variable is not properly affected if
> the code is evaluated in eshell buffer. The eshell buffer is the only
> buffer that I found the above code is not working properly.

process-environment is for invoking other programs from Emacs.  By
contrast, Eshell does not invoke any other program, it is implemented
in Emacs itself.  And process-environment doesn't affect Emacs itself.
That is why you see the difference with other programs, in particular
shells invoked from Emacs.




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

Previous Next


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