Re: master 70964b9: Mention `exec-path' in some process related doc strings

[Michael Albinus <michael.albinus@gmx.de>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Albinus <michael.albinus@gmx.de>
>> Date: Fri, 21 Aug 2020 17:59:13 +0200
>> Cc: Gregory Heytings <ghe@sdf.org>, Lars Ingebrigtsen <larsi@gnus.org>
>>
>> > --- a/src/process.c
>> > +++ b/src/process.c
>> >  :command COMMAND -- COMMAND is a list starting with the program file
>> > -name, followed by strings to give to the program as arguments.
>> > +name, followed by strings to give to the program as arguments.  If the
>> > +program file name is not an absolute file name, `make-process' will
>> > +look for the program file name in `exec-path' (which is a list of
>> > +directories).
>>
>> This is not true in the remote case (default-directory is remote, and
>> :file-handler is non-nil). The program is not looked for; everything in
>> the :command list is used literally.
>>
>> I don't know whether it is worth to explain this subtle difference,
>> though.
>
> Perhaps we could explain that in the ELisp manual.

`exec-path' is discussed in the Elisp manual, node "(elisp) Subprocess Creation".
It seems to be sufficient.

Best regards, Michael.