From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>
Cc: 117@emacsbugs.donarmstrong.com
Subject: bug#117: bug 117: messed up frame parameters
Date: Sun, 28 Dec 2008 00:02:21 -0800 [thread overview]
Message-ID: <002a01c968c2$9d6b7860$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <87r63thynq.fsf@cyd.mit.edu>
> I can't reproduce this using the recipe you gave.
Did you try on MS Windows?
The recipe and code I sent reproduces the problem, for me.
> Please try to reduce the size of the test case. One way to do this is
> to define a function like this:
>
> (defun check-frame-parameters ()
> (let (params (frame-parameters))
> (while params
> (if (assq (caar params) (cdr params))
> (error "Duplicate frame parameter found"))
> (setq params (cdr params)))))
>
> and sprinkle (check-frame-parameters) throughout your code. Then turn
> on debug-on-error, and see when the error first appears.
Please see the test case I sent.
Duplication of frame parameters is only one of the symptoms mentioned, and it
might not even be responsible for the obvious, visual problems I reported.
See also bug #1562 (aka #119) - possibly it's related (dunno). For that bug, the
bug occurs in the C code of `modify-frame-parameters'.
next prev parent reply other threads:[~2008-12-28 8:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 1:32 bug#117: bug 117: messed up frame parameters Chong Yidong
2008-12-28 8:02 ` Drew Adams [this message]
2008-12-28 9:00 ` Chong Yidong
2008-12-28 18:15 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2008-12-28 19:22 grischka
2008-12-28 19:27 ` Drew Adams
2008-07-08 15:02 Drew Adams
2008-07-08 20:54 ` Jason Rumney
2008-07-09 15:27 ` Drew Adams
2008-08-02 20:36 ` Drew Adams
2008-08-02 21:07 ` Jason Rumney
2008-08-02 22:08 ` Drew Adams
2008-08-27 16:41 ` Drew Adams
2008-08-28 15:04 ` Drew Adams
2008-08-30 14:38 ` Drew Adams
2008-10-31 21:05 ` Drew Adams
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='002a01c968c2$9d6b7860$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=117@emacsbugs.donarmstrong.com \
--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).