unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Feature request: Expose system `exec` as a built-in elisp function
Date: Wed, 13 Aug 2014 21:22:42 +0200	[thread overview]
Message-ID: <87d2c4tcsd.fsf@debian.uxu> (raw)
In-Reply-To: mailman.7068.1407955728.1147.help-gnu-emacs@gnu.org

Andrew Pennebaker <andrew.pennebaker@gmail.com> writes:

> One example of the worthiness of exec is cask, an
> Emacs package manager that sometimes wants to fork
> out to an emacs instance, for editing text files.

It seems to me that either you do the job within the
process, or you start a new process to do it.

Are you saying, you want to start a new process, then
have the old process replaced by that process?

If so, why?

-- 
underground experts united


  parent reply	other threads:[~2014-08-13 19:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7022.1407855404.1147.help-gnu-emacs@gnu.org>
2014-08-13 15:29 ` Feature request: Expose system `exec` as a built-in elisp function Barry Margolin
2014-08-13 17:52   ` Andrew Pennebaker
     [not found]   ` <mailman.7066.1407952350.1147.help-gnu-emacs@gnu.org>
2014-08-13 18:45     ` Emanuel Berg
2014-08-13 18:48       ` Andrew Pennebaker
     [not found]       ` <mailman.7068.1407955728.1147.help-gnu-emacs@gnu.org>
2014-08-13 19:22         ` Emanuel Berg [this message]
2014-08-13 20:36         ` Barry Margolin
2014-08-13 21:42           ` Andrew Pennebaker
2014-08-14  6:08             ` Kevin Rodgers
     [not found]           ` <mailman.7080.1407966184.1147.help-gnu-emacs@gnu.org>
2014-08-13 22:16             ` Emanuel Berg
2014-08-13 22:50               ` Andrew Pennebaker
2014-08-14  9:23             ` Barry Margolin
2014-08-14 21:15               ` Emanuel Berg
2014-08-12 14:56 Andrew Pennebaker

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=87d2c4tcsd.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).