Re: call-process should not block process filters from running

[sbaugh@catern.com]

Michael Albinus <michael.albinus@gmx.de> writes:
> sbaugh@catern.com writes:
>
> Hi,
>
>> Also, it's worth noting that process-file makes doing that a little
>> tricky.  process-file already usually runs Lisp while waiting for the
>> process when it's using a remote file name handler, but when it's
>> running locally it just uses call-process.  So users of process-file
>> would need to be converted to start-file-process so that they're
>> uniformly asynchronous.  But, some TRAMP backends support process-file
>> but not start-file-process.  So it's not clear what a programmer should
>> do if they want to synchronously run a process through a file name
>> handler, and they're fine with Lisp running during that.  (Making
>> call-process optionally support running Lisp neatly solves this:
>> process-file users can just bind call-process-run-lisp to t around
>> process-file.)
>
> All of this sounds like a can of worms to Tramp. OMG. Please don't do
> this change.

There's multiple changes being discussed here.  One of them is "change
some users of process-file to use start-file-process instead".  Surely
you don't oppose that change, since it doesn't affect TRAMP internals at
all.