all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Objects that can't be purified during dumping
Date: Sat, 23 Jul 2022 16:27:42 +0300	[thread overview]
Message-ID: <83czdwhsc1.fsf@gnu.org> (raw)
In-Reply-To: <CAM=F=bCAzF0fST46JUPuitaKRsV=8eKOfMizmak+qvz_8ZpTVA@mail.gmail.com> (message from Lynn Winebarger on Sat, 23 Jul 2022 08:19:35 -0400)

> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Sat, 23 Jul 2022 08:19:35 -0400
> 
> In my quest to have a "fully loaded" emacs, I'm attempting to dump a version that loads about 2400 features
> in site-load.el.

Dump how? with the portable dumping?  If so, we don't yet fully
support re-dumping, although it's a goal we'd like to reach.

> Attempting to load email/rfc2047 produces an error to the effect that purecopy does not know how to purify a
> char table (specifically a syntax table).  
> Is there a reason objects that aren't specifically recognized as being "purifiable" can't just be marked as
> pinned like hash table without the purecopy attribute?  I mean, if I put that in the code, are there foreseeable
> bugs that would result?

Pure space will go away at some point, so we are unlikely to invest
any effort into fixing this.



  reply	other threads:[~2022-07-23 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 12:19 Objects that can't be purified during dumping Lynn Winebarger
2022-07-23 13:27 ` Eli Zaretskii [this message]
2022-07-23 13:59   ` Lynn Winebarger
2022-07-23 15:27     ` Eli Zaretskii
2022-07-23 15:55     ` Stefan Monnier
2022-07-24 12:16       ` Lynn Winebarger
2022-07-24 15:07         ` Stefan Monnier
2022-07-24 15:08           ` Eli Zaretskii
2022-08-07 11:27           ` Lynn Winebarger

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=83czdwhsc1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=owinebar@gmail.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 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.