From: lars@nocrew.org (Lars Brinkhoff)
Subject: [TUHS] Emacs and undump
Date: Mon, 27 Feb 2017 21:26:01 +0100 [thread overview]
Message-ID: <86efyjpehy.fsf@molnjunk.nocrew.org> (raw)
In-Reply-To: <31f9e532-c59a-2d3d-1e9b-cef9a216d68e@update.uu.se> (Johnny Billquist's message of "Mon, 27 Feb 2017 21:09:33 +0100")
Johnny Billquist wrote:
> But having the memory around for a program, even if it is not running,
> is actually sometimes very useful. If ITS could handle that, while
> treating them as separate processes, all associated to one terminal,
> and let you select which one you were currently fooling around in,
> while the others stayed around, that is something I don't think I've
> seen elsewhere.
And it's not just a list structure, but a tree. You can e.g. start a
new DDT, which itself can have inferior jobs (subprocesses).
To bring this slightly back on topic, ITS job handling was John Kulp's
inspiration for Unix job control. Control-Z does pretty much the same
thing in both ITS and Unix.
> So, Emacs does it once, and then saves the state at the point where
> you can start editing. But it does not mean that the memory is
> shareable. It's full of various data structures, and code, and that
> will change as you go along editing things as well.
Much is sharable. There's a concept of purification (which also comes
from ITS). A purecopy() function is used in temacs to put read-only
data in a special memory area. That area will become sharable in the
dumped Emacs.
next prev parent reply other threads:[~2017-02-27 20:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.346.1488208394.3779.tuhs@minnie.tuhs.org>
2017-02-27 20:09 ` Johnny Billquist
2017-02-27 20:26 ` Lars Brinkhoff [this message]
2017-02-27 21:06 ` Johnny Billquist
[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.334.1488132096.3779.tuhs@minnie.tuhs.org>
2017-02-26 19:16 ` David
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
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=86efyjpehy.fsf@molnjunk.nocrew.org \
--to=lars@nocrew.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).