From: david@kdbarto.org (David)
Subject: [TUHS] Emacs and undump
Date: Sun, 26 Feb 2017 11:16:54 -0800 [thread overview]
Message-ID: <141DC1F7-C4AA-4EF4-8CBE-E99845326D7B@kdbarto.org> (raw)
In-Reply-To: <mailman.334.1488132096.3779.tuhs@minnie.tuhs.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
I ported GNU Emacs to the Celerity product line mostly because most of the programmers there wanted it over vi. Not me, I’m a vi guy.
I remember that GNU Emacs launched the first time and then dumped itself out as a core file. Each subsequent launch would then ‘undump’ itself back into memory. All this because launching emacs the first time required compiling all that lisp code.
Does anyone else remember this?
David
next parent reply other threads:[~2017-02-26 19:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.334.1488132096.3779.tuhs@minnie.tuhs.org>
2017-02-26 19:16 ` David [this message]
2017-02-26 19:28 ` Mantas Mikulėnas
2017-02-27 6:41 ` Tim Bradshaw
2017-02-27 7:19 ` Lars Brinkhoff
2017-02-27 7:26 ` Warner Losh
2017-02-27 8:12 ` Nick Downing
2017-02-27 14:33 ` Derek Fawcus
2017-02-27 14:50 ` Nick Downing
2017-02-27 15:43 ` Derek Fawcus
2017-02-27 16:43 ` Joerg Schilling
[not found] ` <CAH1jEzZjvOhHnbvsWcw8gbx9d_W47DbBidYd_tteCr5dC6H2ng@mail.gmail.com>
2017-02-28 0:02 ` Nick Downing
2017-02-27 12:59 ` tfb
2017-02-27 10:35 ` Joerg Schilling
2017-02-27 15:13 ` Tony Finch
[not found] <mailman.342.1488180370.3779.tuhs@minnie.tuhs.org>
2017-02-27 10:24 ` Johnny Billquist
2017-02-27 10:30 ` Lars Brinkhoff
2017-02-27 10:47 ` Johnny Billquist
2017-02-27 14:04 ` Arthur Krewat
2017-02-28 11:55 ` Ronald Natalie
[not found] <mailman.346.1488208394.3779.tuhs@minnie.tuhs.org>
2017-02-27 20:09 ` Johnny Billquist
2017-02-27 20:26 ` Lars Brinkhoff
2017-02-27 21:06 ` Johnny Billquist
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=141DC1F7-C4AA-4EF4-8CBE-E99845326D7B@kdbarto.org \
--to=david@kdbarto.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 NNTP newsgroup(s).