From: "John Wiegley" <johnw@gnu.org>
To: dancol@dancol.org
Cc: Paul Eggert <eggert@cs.ucla.edu>, Tom Tromey <tom@tromey.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: pdumping "into" the executable
Date: Mon, 26 Feb 2018 23:55:54 -0800 [thread overview]
Message-ID: <m2woyyj27p.fsf@newartisans.com> (raw)
In-Reply-To: <99612a866c6e99d2a1be29d49c9dee53.squirrel@dancol.org> (dancol's message of "Mon, 26 Feb 2018 16:16:20 -0800")
>>>>> "d" == dancol <dancol@dancol.org> writes:
d> That is exactly the use case that we'll be able to support again. IMHO, it
d> should be automatic, although I don't know exactly what the startup-file
d> dependency tracking arrangement is going to look like.
Will we gain an SBCL-like `save-lisp-and-die' function?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2018-02-27 7:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:38 pdumping "into" the executable Stefan Monnier
2018-02-26 17:00 ` Daniel Colascione
2018-02-26 21:10 ` Tom Tromey
2018-02-26 21:18 ` dancol
2018-02-26 22:07 ` Paul Eggert
2018-02-26 22:22 ` Daniel Colascione
2018-02-26 23:17 ` Paul Eggert
2018-02-26 23:34 ` dancol
2018-02-26 23:41 ` dancol
2018-02-27 0:09 ` Drew Adams
2018-02-27 0:16 ` dancol
2018-02-27 7:55 ` John Wiegley [this message]
2018-02-27 13:47 ` Dmitry Gutov
2018-02-27 14:47 ` Stefan Monnier
2018-02-27 18:32 ` John Wiegley
2018-02-26 22:34 ` Clément Pit-Claudel
2018-02-26 22:47 ` Daniel Colascione
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=m2woyyj27p.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=dancol@dancol.org \
--cc=drew.adams@oracle.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tom@tromey.com \
/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).