From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org, dpittman@fb.com
Subject: Re: Environment variables for remote processes
Date: Mon, 17 Nov 2014 21:15:52 -0500 [thread overview]
Message-ID: <jwvh9xxnto9.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87h9xxvf31.fsf_-_@gmx.de> (Michael Albinus's message of "Mon, 17 Nov 2014 19:48:02 +0100")
>> Nothing wrong with it. The problem is that Tramp ignores those
>> let-bindings because it fails to propagate this environment to its
>> remote sub-processed.
> The problem is, that not all settings of process-environment might be
> desired on remote hosts. process-environment keeps *local* variables.
I'm not so sure. We're talking here about the settings which are in
process-environment but not in (default-toplevel-value
'process-environment), so these are all settings added via let-binding
process-environment, and in all the cases I can think of, these seem to
be either useful or harmless to propagate.
But maybe we need to tweak the heuristic by excluding some env-vars
(like PATH).
> Furthermore, some remote settings might be requested which are not in
> process-environment by default.
Not sure what you're referring to here, but it seems like a different
issue than the one at hand (which is to propagate let-bound
process-environment values).
> tramp-sh-handle-process-file does not start a new process, it reuses the
> existing one. The propagation to the remote sub-process must ensure,
> that those settings are not permanent. Via a subshell, or alike.
Of course.
Stefan
next prev parent reply other threads:[~2014-11-18 2:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <030C5AEB-C009-4995-B153-6EECD44802C8@fb.com>
[not found] ` <87y4rkhdt6.fsf@gmx.de>
[not found] ` <87y4rf2jtx.fsf@gmx.de>
[not found] ` <jwv4mu3rniq.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87r3x6eq8w.fsf@gmx.de>
[not found] ` <jwvh9y23640.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87mw7rtnxg.fsf@gmx.de>
[not found] ` <83a93rduz4.fsf@gnu.org>
[not found] ` <jwv4mtyua90.fsf-monnier+emacsbugs@gnu.org>
2014-11-17 18:48 ` Environment variables for remote processes (was: bug#18940: 24.4; vc-hg does not disable pager, leading to hangs (at least with tramp)) Michael Albinus
2014-11-18 2:15 ` Stefan Monnier [this message]
2014-11-18 19:14 ` Environment variables for remote processes Michael Albinus
2014-11-18 21:24 ` Stefan Monnier
2014-11-18 21:45 ` Michael Albinus
2014-11-19 3:16 ` Stefan Monnier
2014-11-19 15:12 ` andres.ramirez
2014-11-23 10:22 ` Michael Albinus
2014-11-19 18:18 ` Michael Albinus
2014-11-19 18:31 ` Michael Albinus
2014-11-20 4:29 ` Stefan Monnier
2014-11-20 15:52 ` Michael Albinus
2014-11-21 2:46 ` Stefan Monnier
2014-11-22 11:43 ` Michael Albinus
2014-11-22 16:33 ` Stefan Monnier
2014-11-22 16:49 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh9xxnto9.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dpittman@fb.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).