unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Query about call-process
Date: Sun, 01 Apr 2018 17:21:37 +0000	[thread overview]
Message-ID: <CAArVCkS994RFjr_9gVmvwtYSxwV+qjG3TMmrnmY6HjsxuRwB_Q@mail.gmail.com> (raw)
In-Reply-To: <83fu4g8zfv.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> schrieb am Sa., 31. März 2018 um 09:41 Uhr:

> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Fri, 30 Mar 2018 21:24:00 +0000
> > Cc: help-gnu-emacs@gnu.org
> >
> > Eli Zaretskii <eliz@gnu.org> schrieb am Fr., 30. März 2018 um 23:22 Uhr:
> >
> >  > From: Philipp Stephani <p.stephani2@gmail.com>
> >  > Date: Fri, 30 Mar 2018 19:44:25 +0000
> >  > Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> >  >
> >  > Though the argument is a bit weird because `make-process' can do
> exactly
> >  > that. It would just require changing `call-process' to use a select
> loop to
> >  > achieve the same effect.
> >
> >  Once you change call-process to do the same as make-process, what
> >  would be the difference between those two?
> >
> > 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.


  reply	other threads:[~2018-04-01 17:21 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 [this message]
2018-04-01 17:29           ` Eli Zaretskii

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=CAArVCkS994RFjr_9gVmvwtYSxwV+qjG3TMmrnmY6HjsxuRwB_Q@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=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).