Re: `call-process', to a string

[Garreau\, Alexandre]

On 2018/10/30 at 02:25, Basil L. Contovounesios wrote:
> "Garreau, Alexandre" <address@hidden> writes:
>
>> In the `call-process' docstring related to the argument about output,
>> there’s nothing related to a string:
>>
>>> Insert output in DESTINATION before point; t means current buffer; nil for 
>>> DESTINATION
>>>  means discard it; 0 means discard and don’t wait; and ‘(:file FILE)’, where
>>>  FILE is a file name string, means that it should be written to that file
>>>  (if the file already exists it is overwritten).
>>> DESTINATION can also have the form (REAL-BUFFER STDERR-FILE); in that case,
>>> REAL-BUFFER says what to do with standard output, as above,
>>> while STDERR-FILE says what to do with standard error in the child.
>>> STDERR-FILE may be nil (discard standard error output),
>>> t (mix it with ordinary output), or a file name string.
>>
>> I also notice it is not documented that DESTINATION may be a buffer, in
>> which case the output is inserted in the said buffer (I checked).
>
> Indeed this does not seem to be documented in the docstring of
> call-process, but it is documented in the manual under
> '(elisp) Synchronous Processes'.

It’s odd.