GNU bug report logs -
#42704
Documentation of call-process
Previous Next
Reported by: Gregory Heytings <ghe <at> sdf.org>
Date: Tue, 4 Aug 2020 09:30:01 UTC
Severity: minor
Tags: fixed
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #11 received at 42704 <at> debbugs.gnu.org (full text, mbox):
>
>> The documentation of 'call-process' doe not make reference to the
>> variable 'exec-path'. It should.
>
> The ELisp manual says that, see the node "Subprocess Creation". This
> isn't specific to call-process, that variable is used by all the
> functions that create subprocesses.
>
Indeed. I still believe that adding the sentence "If PROGRAM is not an
absolute file name, the variable exec-path contains a list of directories
to search." in the docstring of call-process (and a similar sentence in
the docstrings of make-process and call-process-region) would be useful.
>
>> Using '(setenv "PATH" "...")' does not have the expected effect for
>> 'call-process'. The environment variable "PATH" is correctly updated,
>> the variable 'process-environment' is also updated, but what
>> 'call-process' actually uses to locate the executable is the variable
>> 'exec-path'.
>
> The changes to the environment variables only affect the environment
> passed to subprocesses, they don't affect the environment of the Emacs
> process itself.
>
Indeed. Creating a subprocess is in between the two (Emacs and the
subprocess), and I at least would have expected that setting "PATH" would
have changed the path in which the program executable is searched.
Gregory
This bug report was last modified 4 years and 272 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.