From: martin rudalics <rudalics@gmx.at>
To: npostavs@users.sourceforge.net
Cc: 25511@debbugs.gnu.org, Katsumi Yamaoka <yamaoka@jpl.org>
Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?
Date: Tue, 06 Jun 2017 08:38:26 +0200 [thread overview]
Message-ID: <59364DE2.2010501@gmx.at> (raw)
In-Reply-To: <87o9u2x9ww.fsf@users.sourceforge.net>
>>> Is there something more to do with this bug?
>>
>> Is there something more to do with bug#25521?
>
> Just the question of whether we should add back some delay after frame
> creation, the original problem there is easily fixed by changing the
> user code. I gather from your question that it's the same for this bug?
Yes. Problems in this area have existed for a long time. Practically
all of them result from code using ‘make-frame’ followed by code that
immediately tries to read or modify properties of the frame to create.
For example, Bug#25511 has
(let ((frame (make-frame)))
(modify-frame-parameters frame ...
while Bug#25521 has
(make-frame '((name . "foo")
...
(select-frame-by-name "foo")
and, for example, Bug#25943 has
(let ((simple-frame (make-frame `((name . "Simple Frame")
...
(unwind-protect
(while (progn
(set-frame-size simple-frame ...
IIRC there were more similar reports. BTW Bug#25943 was reported for an
Emacs 25.1 GTK build hence before you removed the delay to fix Bug#24091.
We could introduce some customizable delay and, whenever a bug in this
area is reported, tell people to increase that delay. If the bug does
not disappear after the delay has gotten pretty large, we have a more
nasty problem. Otherwise, we have perfidiously shifted responsibility
to the user.
martin
next prev parent reply other threads:[~2017-06-06 6:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 7:28 bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter? Katsumi Yamaoka
2017-01-23 8:03 ` martin rudalics
2017-01-23 9:01 ` Katsumi Yamaoka
2017-01-23 10:28 ` martin rudalics
2017-01-23 22:54 ` Katsumi Yamaoka
2017-01-24 0:45 ` Katsumi Yamaoka
2017-01-24 7:46 ` martin rudalics
2017-01-24 9:18 ` Katsumi Yamaoka
2017-01-24 9:37 ` martin rudalics
2017-06-05 12:57 ` npostavs
2017-06-05 13:36 ` martin rudalics
2017-06-06 0:00 ` npostavs
2017-06-06 6:38 ` martin rudalics [this message]
2017-01-24 7:46 ` martin rudalics
2017-01-23 17:27 ` Noam Postavsky
2017-01-23 18:01 ` martin rudalics
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=59364DE2.2010501@gmx.at \
--to=rudalics@gmx.at \
--cc=25511@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=yamaoka@jpl.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).