all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: SK Kim <tttuuu888@gmail.com>
Cc: 30134@debbugs.gnu.org
Subject: bug#30134: ehsell and process-environment variable
Date: Tue, 16 Jan 2018 05:40:33 +0200	[thread overview]
Message-ID: <83shb6xyha.fsf@gnu.org> (raw)
In-Reply-To: <CAKYNWwS3AV9-czw2ZLpKPNRkHvK0jKKHayy8_NPzx+M-SWPF4Q@mail.gmail.com> (message from SK Kim on Tue, 16 Jan 2018 11:31:27 +0900)

> From: SK Kim <tttuuu888@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.





  reply	other threads:[~2018-01-16  3:40 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 [this message]
     [not found]   ` <CAKYNWwSCjTu=tU=Kx9x8-7RxaHyeaXE6OpkEBvWvNQGVM_GsFA@mail.gmail.com>
2018-01-16 17:04     ` Eli Zaretskii
2018-01-16 18:03   ` Glenn Morris
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=83shb6xyha.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30134@debbugs.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.