From: Lynn Winebarger <owinebar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Regression in dump-emacs-portable
Date: Wed, 22 Feb 2023 21:41:15 -0500 [thread overview]
Message-ID: <CAM=F=bAivXqZehHC5Jrsp9XbkkT09pJn2TdLg1AK1ky7L5_XKA@mail.gmail.com> (raw)
In-Reply-To: <CAM=F=bDO51bUSaC9J4YO9hzYDAMM8QEMqwxsXSPMSX4FKtB7uQ@mail.gmail.com>
On Tue, Feb 21, 2023 at 9:21 AM Lynn Winebarger <owinebar@gmail.com> wrote:
> On Sat, Feb 18, 2023, 2:07 AM Eli Zaretskii <eliz@gnu.org> wrote:
>> > I'll take a shot at a more thorough rewrite of the customization
>> > system to properly support redumping this weekend and send another
>> > patch.
>>
>> I'm not sure this is the tree we should be barking up. The problem is
>> more general than just delayed-initialization of some defcustoms.
>
>
> I wrote about 95% of this over the weekend, most of which is the efficient solver for dependency ordering of the customization variables set at startup. I'll finish it up in the next couple of evenings and post the patch in a bug report/feature request.
>
> My immediate concern is being able to use the current re-dumping facility more effectively.
I've posted a patch at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61721 It's true there
are not a lot of these customizations in the baseline dump, but there
are many more when additional libraries are redumped.
However, the problem with dumping overlays is very troublesome for
creating comprehensive redumps.
next prev parent reply other threads:[~2023-02-23 2:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 0:51 Regression in dump-emacs-portable Lynn Winebarger
2023-02-14 1:13 ` Lynn Winebarger
2023-02-14 14:23 ` Eli Zaretskii
2023-02-14 23:26 ` Lynn Winebarger
2023-02-15 12:42 ` Eli Zaretskii
2023-02-16 9:31 ` Lynn Winebarger
2023-02-16 9:54 ` Lynn Winebarger
2023-02-16 15:05 ` Lynn Winebarger
2023-02-16 15:34 ` Eli Zaretskii
2023-02-16 23:45 ` Lynn Winebarger
2023-02-17 13:22 ` Lynn Winebarger
2023-02-17 14:31 ` Eli Zaretskii
2023-02-17 23:44 ` Lynn Winebarger
2023-02-18 7:07 ` Eli Zaretskii
2023-02-21 14:21 ` Lynn Winebarger
2023-02-23 2:41 ` Lynn Winebarger [this message]
2023-02-23 13:21 ` Lynn Winebarger
2023-02-16 15:46 ` Eli Zaretskii
2023-02-17 1:29 ` Lynn Winebarger
2023-02-17 3:19 ` Lynn Winebarger
2023-02-17 4:10 ` Lynn Winebarger
2023-02-17 5:21 ` Po Lu
2023-02-17 12:57 ` Lynn Winebarger
2023-02-23 15:08 ` Gregory Heytings
2023-02-23 22:32 ` Lynn Winebarger
2023-02-25 4:11 ` Richard Stallman
2023-02-25 4:11 ` Richard Stallman
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='CAM=F=bAivXqZehHC5Jrsp9XbkkT09pJn2TdLg1AK1ky7L5_XKA@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).