From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: 34114@debbugs.gnu.org, karl@karlotness.com, kaushal.modi@gmail.com
Subject: bug#34114: 27.0.50: pdumper and themes with Emacs daemon
Date: Wed, 23 Jan 2019 05:43:26 +0200 [thread overview]
Message-ID: <83r2d482e9.fsf@gnu.org> (raw)
In-Reply-To: <8f223d05-fd50-4ea8-c92e-6dd574642175@dancol.org> (message from Daniel Colascione on Tue, 22 Jan 2019 17:41:34 -0800)
> Cc: karl@karlotness.com, 34114@debbugs.gnu.org, kaushal.modi@gmail.com
> From: Daniel Colascione <dancol@dancol.org>
> Date: Tue, 22 Jan 2019 17:41:34 -0800
>
> > What is special about frames that precludes them from being recorded
> > by the pdumper?
>
> Frames contain instance-specific state, and I don't think it makes sense
> to try to pretend that individual frames survive from one Emacs
> invocation to another.
Sorry, I still don't think I understand: what is that
instance-specific state, in terms of members of the frame object, or
its attributes?
next prev parent reply other threads:[~2019-01-23 3:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 11:15 bug#34114: 27.0.50: pdumper and themes with Emacs daemon Karl Otness
2019-01-17 20:01 ` Kaushal Modi
2019-01-17 20:38 ` Kaushal Modi
2019-01-18 23:02 ` Karl Otness
2019-01-18 23:23 ` Daniel Colascione
2019-01-18 23:37 ` Karl Otness
2019-01-18 23:49 ` Daniel Colascione
2019-01-19 0:09 ` Karl Otness
2019-01-19 7:05 ` Eli Zaretskii
2019-01-21 22:59 ` Daniel Colascione
2019-01-22 16:28 ` Kaushal Modi
2019-01-22 16:45 ` Eli Zaretskii
2019-01-23 1:41 ` Daniel Colascione
2019-01-23 3:43 ` Eli Zaretskii [this message]
2019-01-23 4:05 ` Daniel Colascione
2019-01-23 5:32 ` Eli Zaretskii
2019-01-23 6:48 ` Daniel Colascione
2019-01-24 15:11 ` Eli Zaretskii
2019-01-24 19:22 ` Karl Otness
2019-01-26 10:22 ` Eli Zaretskii
2019-01-27 18:40 ` Kaushal Modi
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=83r2d482e9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34114@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=karl@karlotness.com \
--cc=kaushal.modi@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 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).