Re: Environment variables for remote processes

[Stefan Monnier]

>> 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