unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: Suggested change in net/browse-url.el
Date: 05 Apr 2004 02:36:27 +0200	[thread overview]
Message-ID: <m33c7jclbo.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1BAAQf-0003RG-He@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

>     Since I use 0 here, the output of calling the process is discarded
>     and Emacs does _not_ wait.
> 
> You're right.  Sorry for not noticing that.
> 
>     In fact, this way of using call-process is the _only_ way to start a
>     process in the background without getting an associated process object
>     within Emacs.  It is a bit confusing that the API for starting a
>     particularly asynchronous kind of process is hidden in the function
>     used normally for starting synchronous processes,
> 
> Good point.  We could add a new function for this: fork-process.  What
> do people think of that?

It would be ok to add it (e.g. in subr.el), but fork-process would be
a mis-leading name for it IMO -- fork means that you get two identical
processes (i.e.  two emacs processes running).

I think call-process-nowait would be better (we already have an analogy
with open-network-stream-nowait).  It would simply be a macro which calls
call-process with 0 BUFFER argument -- but with a specific doc string.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-04-05  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 17:24 Suggested change in net/browse-url.el David Kastrup
2004-04-03  1:30 ` Richard Stallman
2004-04-03  1:44   ` David Kastrup
2004-04-04 16:25     ` Richard Stallman
2004-04-05  0:36       ` Kim F. Storm [this message]
2004-04-05  2:22         ` David Kastrup

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=m33c7jclbo.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=dak@gnu.org \
    --cc=emacs-devel@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.
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).