From: Michael Albinus <michael.albinus@gmx.de>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: Philipp Stephani <p.stephani2@gmail.com>,
jonas@bernoul.li, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Remote asynchronous processes
Date: Tue, 14 Apr 2020 16:28:54 +0200 [thread overview]
Message-ID: <87lfmyywd5.fsf@gmx.de> (raw)
In-Reply-To: <CAGK7Mr5pHdVo2g0kfEjXcV6qaEp=AcfnM2No-x+qfjqsG+wyNg@mail.gmail.com> (Philippe Vaucher's message of "Tue, 14 Apr 2020 14:34:37 +0200")
Philippe Vaucher <philippe.vaucher@gmail.com> writes:
Hi Philippe,
> So basically what you need to know is how `make-process` is used in
> the wild. If that helps, magit only uses `start-file-process` and
> never `make-process`.
>
> You could try to grep other common libraries to see, on the ones I
> follow the only reference to `make-process` I found was in counsel's
> `counsel--call` doc string, to mention it uses the same arguments list
> (but never actually calls it).
I don't believe that make-process is used for remote processes
already. This feature has been added in Emacs 27, see etc/NEWS:
--8<---------------cut here---------------start------------->8---
** 'make-process' now takes a keyword argument ':file-handler'; if
that is non-nil, it will look for a file name handler for the current
buffer's 'default-directory' and invoke that file name handler to make
the process. That way 'make-process' can start remote processes.
--8<---------------cut here---------------end--------------->8---
If we change the behavior as proposed, we should add a warning about the
prospective change in Emacs 28 here.
> Kind regards,
> Philippe
Best regards, Michael.
next prev parent reply other threads:[~2020-04-14 14:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 10:19 Remote asynchronous processes Michael Albinus
2020-04-13 20:32 ` Philippe Vaucher
2020-04-14 9:03 ` Michael Albinus
2020-04-14 12:34 ` Philippe Vaucher
2020-04-14 14:28 ` Michael Albinus [this message]
2020-08-04 17:00 ` Philipp Stephani
2020-04-14 14:48 ` Stefan Monnier
2020-04-14 15:30 ` Michael Albinus
2020-08-04 17:01 ` Philipp Stephani
2020-08-04 16:56 ` Philipp Stephani
2020-08-04 17:35 ` Michael Albinus
2020-08-10 14:42 ` Philipp Stephani
2020-05-06 11:59 ` Michael Albinus
2020-08-04 16:48 ` Philipp Stephani
2020-08-04 17:31 ` Michael Albinus
2020-08-10 14:56 ` Philipp Stephani
-- strict thread matches above, loose matches on Subject: below --
2020-07-29 16:58 Felipe Lema
2020-07-31 10:22 ` Michael Albinus
2020-08-04 12:27 ` Michael Albinus
2020-08-04 16:06 ` Felipe Lema
2020-08-06 19:08 ` Sean Whitton
2020-08-09 7:22 ` Michael Albinus
2020-08-09 14:47 ` Philipp Stephani
2020-08-09 17:06 ` Michael Albinus
2020-08-12 10:46 ` Michael Albinus
2020-08-21 22:28 ` Sean Whitton
2020-08-07 16:28 ` Philipp Stephani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfmyywd5.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--cc=p.stephani2@gmail.com \
--cc=philippe.vaucher@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).