From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Query about call-process
Date: Sun, 01 Apr 2018 20:29:55 +0300 [thread overview]
Message-ID: <83efjy7s30.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkS994RFjr_9gVmvwtYSxwV+qjG3TMmrnmY6HjsxuRwB_Q@mail.gmail.com> (message from Philipp Stephani on Sun, 01 Apr 2018 17:21:37 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 01 Apr 2018 17:21:37 +0000
> Cc: help-gnu-emacs@gnu.org
>
> > call-process would still wait for the process to finish.
>
> make-process can do that, too.
>
> How? Probably it's some combination of make-process, process-send-region, and accept-process-output,
> but I haven't yet figured out a combination that doesn't make Emacs hang.
Calling call-process also "hangs" Emacs until the process exits. So
there's no difference in behavior.
prev parent reply other threads:[~2018-04-01 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 18:47 Query about call-process Narendra Joshi
2018-03-30 19:44 ` Philipp Stephani
2018-03-30 21:21 ` Eli Zaretskii
2018-03-30 21:24 ` Philipp Stephani
2018-03-31 7:41 ` Eli Zaretskii
2018-04-01 17:21 ` Philipp Stephani
2018-04-01 17:29 ` Eli Zaretskii [this message]
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=83efjy7s30.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).