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: Thu, 14 Aug 2014 23:15:48 +0200 [thread overview]
Message-ID: <87zjf6hiwr.fsf@debian.uxu> (raw)
In-Reply-To: barmar-75B4F0.05231914082014@news.eternal-september.org
Barry Margolin <barmar@alum.mit.edu> writes:
> But you still haven't answered: why should editing
> the cask files in a new Emacs instance require
> replacing the original Emacs instance, instead of
> running both of them concurrently? This "exec"
> operation will need to perform all the actions done
> during kill-emacs, like asking about saving modified
> buffers, killing running processes, etc.
Indeed, why would anyone like to kill Emacs? It is
inconceivable :)
--
underground experts united
next prev parent reply other threads:[~2014-08-14 21:15 UTC|newest]
Thread overview: 16+ 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
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 [this message]
2014-08-13 13:44 Andrew Pennebaker
2014-08-13 15:57 ` Stefan Monnier
2014-08-13 18:27 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjf6hiwr.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.