From: Andrew Pennebaker <andrew.pennebaker@gmail.com>
To: Barry Margolin <barmar@alum.mit.edu>
Cc: Emacs Help <help-gnu-emacs@gnu.org>
Subject: Re: Feature request: Expose system `exec` as a built-in elisp function
Date: Wed, 13 Aug 2014 12:52:26 -0500 [thread overview]
Message-ID: <CAHXt_SXNTKSviiRX0ELgCjq9MfRvY9S7jgzAQ6qsRDwjNrK7+Q@mail.gmail.com> (raw)
In-Reply-To: <barmar-E27F7E.11290913082014@news.eternal-september.org>
That's what I thought, at first. exec has the additional semantic that it
replaces the current process with the system call, so it's more efficient
for certain tasks.
On Wed, Aug 13, 2014 at 10:29 AM, Barry Margolin <barmar@alum.mit.edu>
wrote:
> In article <mailman.7022.1407855404.1147.help-gnu-emacs@gnu.org>,
> Andrew Pennebaker <andrew.pennebaker@gmail.com> wrote:
>
> > Could the next version of Emacs / elisp expose `exec` as a built-in elisp
> > function?
>
> Isn't this pretty much what start-process does?
>
> >
> > The Unix `exec` semantic is useful for Cask and other Emacs-related
> > programs, but is currently not accessible via elisp. If it were, elisp
> > programs could, for example, begin an Emacs editing session even though
> the
> > elisp program itself was originally run using emacs.
>
> I can't figure out what you're talking about here.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
>
--
Cheers,
Andrew Pennebaker
www.yellosoft.us
next prev parent reply other threads:[~2014-08-13 17:52 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 [this message]
[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
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=CAHXt_SXNTKSviiRX0ELgCjq9MfRvY9S7jgzAQ6qsRDwjNrK7+Q@mail.gmail.com \
--to=andrew.pennebaker@gmail.com \
--cc=barmar@alum.mit.edu \
--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).