From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 6713@debbugs.gnu.org
Subject: bug#6713: initial-frame-alist params applied to all frames
Date: Mon, 25 Oct 2010 16:25:22 -0400 [thread overview]
Message-ID: <jwvaam2m3ec.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zkxi6v2x.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 23 Jul 2010 12:07:02 -0400")
>> With a .emacs that contains just:
>> (setq initial-frame-alist '((background-color . "grey75")))
>> start "emacs" and then hit C-x 5 2. Notice that the second frame also
>> has a grey75 background.
> Hmm, I can't reproduce this. For me, the second frame is white. This
> is with latest bzr sources, and `xrdb -remove' before running Emacs.
I'm still seeing this bug (which appeared back when you changed the
default-frame-alist handling):
% src/emacs -Q --eval '(setq initial-frame-alist (quote ((background-color . "grey75"))))'
C-x 5 2
Gives me 2 frames, both with a grey75 background. If I change grey75 to
something else (like "red"), I get a red background in both frames.
But I recently noticed that the bug was not present on one of my
machine; which happens to be one where I was running a mix of Debian
"stable"&"testing" (because of a problem in the "testing" version of the
X11 driver). I've now upgraded it back to "testing" and the bug is now
present there as well, so it appears to also depend on the version of
some library (probably libX11 since the bug appears both with Gtk and
Lucid toolkits).
Also the bug is not present in the emacs-23 branch, so while the version
of some library might matter, Emacs's own code also matters.
Stefan
next prev parent reply other threads:[~2010-10-25 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 13:39 bug#6713: initial-frame-alist params applied to all frames Stefan Monnier
2010-07-23 16:07 ` Chong Yidong
2010-07-26 0:23 ` Stefan Monnier
2010-10-25 20:25 ` Stefan Monnier [this message]
2011-01-13 4:42 ` Stefan Monnier
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=jwvaam2m3ec.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6713@debbugs.gnu.org \
--cc=cyd@stupidchicken.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).