bug#30862: 25.3; Need variant of `make-process' that uses file name handlers

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

Philipp Stephani <p.stephani2@gmail.com> writes:

Hi Philipp,

> I don't see why call-process and make-process should behave
> differently in this regard. For call-process and start-process the
> caller has to explicitly opt in into applying file name handlers (by
> calling different functions); presumably because people consider it
> too dangerous to accidentally start random processes on remote
> machines. Why should make-process be different?

In general, file name handlers are invoked silently, w/o the need to
adapt the using packages. `call-process' and `start-process' are
exceptions, because sometimes it isn't desired to invoke a file name
handler, even if `default-directory' is remote. Therefore, the new
functions.

`make-process' fits into this category. Whether a new function to be
applied, or an additional argument, doesn't make a difference. The
latter was not possible for `call-process' and `start-process'.

We have now your patch (thanks!), let's continue this way.

Best regards, Michael.