From: Michael Albinus Date: Sun, 23 Nov 2014 11:33:45 +0000 (+0100) Subject: * tramp.texi (Remote processes): Let-bind environment variables to X-Git-Tag: emacs-25.0.90~2635^2~374 X-Git-Url: https://code.delx.au/gnu-emacs/commitdiff_plain/600f3d0528bf9acfea89985755d94e05a78df341 * tramp.texi (Remote processes): Let-bind environment variables to `process-environment' when running `process-file' or `start-file-process'. --- diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog index 0e9300ab14..e9029d59c2 100644 --- a/doc/misc/ChangeLog +++ b/doc/misc/ChangeLog @@ -1,3 +1,9 @@ +2014-11-23 Michael Albinus + + * tramp.texi (Remote processes): Let-bind environment variables to + `process-environment' when running `process-file' or + `start-file-process'. + 2014-11-19 Ivan Shmakov * eww.texi (Basics): Document `eww-history-limit'. diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi index a245de8239..8eb25c690e 100644 --- a/doc/misc/tramp.texi +++ b/doc/misc/tramp.texi @@ -2711,6 +2711,21 @@ following code in your @file{.emacs}: (setq tramp-remote-process-environment process-environment)) @end lisp +When running @code{process-file} or @code{start-file-process} on a +remote @code{default-directory}, the default settings in +@code{process-environment} are not used as it is the case for local +processes. However, if you need environment variables other than set +in @code{tramp-remote-process-environment}, you can let-bind them to +@code{process-environment}. Only those variables will be set then: + +@lisp +(let ((process-environment (cons "HGPLAIN=1" process-environment))) + (process-file @dots{})) +@end lisp + +This works only for environment variables which are not set already in +@code{process-environment}. + If you use other @value{emacsname} packages which do not run out-of-the-box on a remote host, please let us know. We will try to integrate them as well. @xref{Bug Reports}.