From: Chong Yidong <cyd@stupidchicken.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 911@emacsbugs.donarmstrong.com, Ian Miller <ian@soroban.fastmail.fm>
Subject: bug#911: 23.0.60; custom-set-faces causes "New Frame" to fail
Date: Thu, 25 Sep 2008 10:31:16 -0400 [thread overview]
Message-ID: <878wtgnvpn.fsf@cyd.mit.edu> (raw)
In-Reply-To: <48DB55BF.5040803@gmx.at> (martin rudalics's message of "Thu, 25 Sep 2008 11:11:27 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> How about defining a variable `frame-set-background-mode-bg-mode'? If
>> it's nil, frame-set-background-mode uses the existing calculation to
>> determine whether it's light or dark; if it's non-nil, it uses that
>> existing value. This should prevent the oscillation.
>
> But who would be responsible for setting and resetting that variable?
> Hardly `frame-set-background-mode' itself. Would we make this a frame
> parameter so the command loop can reset it and allow to change it once
> and only once for a command? Otherwise, we might risk reentering the
> loop with the next call of `frame-set-background-mode'.
Why not in frame-set-background-mode itself? Then, when it's set,
subsequent calls to that function could be no-ops.
> BTW, it seems you already closed bug#911 ...
Sorry, I must have mistyped when trying to close a different bug.
Reopened.
next prev parent reply other threads:[~2008-09-25 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y71hthoc.fsf@cyd.mit.edu>
2008-09-07 11:36 ` bug#911: 23.0.60; custom-set-faces causes "New Frame" to fail (max-specpdl-size) Ian Miller
2008-09-24 20:30 ` bug#911: marked as done (23.0.60; custom-set-faces causes "New Frame" to fail (max-specpdl-size)) Emacs bug Tracking System
2008-10-02 20:30 ` Emacs bug Tracking System
2008-09-25 9:11 ` bug#911: 23.0.60; custom-set-faces causes "New Frame" to fail martin rudalics
2008-09-25 14:31 ` Chong Yidong [this message]
2008-09-25 15:17 ` martin rudalics
2008-09-28 21:13 Chong Yidong
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=878wtgnvpn.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=911@emacsbugs.donarmstrong.com \
--cc=ian@soroban.fastmail.fm \
--cc=rudalics@gmx.at \
/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).