From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30134@debbugs.gnu.org, SK Kim <tttuuu888@gmail.com>
Subject: bug#30134: ehsell and process-environment variable
Date: Tue, 16 Jan 2018 13:03:14 -0500 [thread overview]
Message-ID: <r6d129vfz1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83shb6xyha.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Jan 2018 05:40:33 +0200")
Eli Zaretskii wrote:
>> 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.
[...]
> 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.
I don't think that's relevant to this report, where a bash shell is
being invoked, it just happens to be launched from an eshell buffer.
eshell seems to have some special handling for process-environment,
which is (presumably) the cause of this difference from other buffers.
next prev parent reply other threads:[~2018-01-16 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 2:31 bug#30134: ehsell and process-environment variable SK Kim
2018-01-16 3:40 ` Eli Zaretskii
[not found] ` <CAKYNWwSCjTu=tU=Kx9x8-7RxaHyeaXE6OpkEBvWvNQGVM_GsFA@mail.gmail.com>
2018-01-16 17:04 ` Eli Zaretskii
2018-01-16 18:03 ` Glenn Morris [this message]
2018-01-18 6:11 ` SK Kim
2018-01-18 17:49 ` Glenn Morris
2018-01-18 17:54 ` Glenn Morris
2018-01-19 1:33 ` SK Kim
2018-01-18 17:52 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=r6d129vfz1.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=30134@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tttuuu888@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.