From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34317@debbugs.gnu.org
Subject: bug#34317: 26.1.90; Wrong unbinding order in x_consider_frame_title
Date: Sat, 23 Feb 2019 15:00:31 +0100 [thread overview]
Message-ID: <5C7151FF.5070504@gmx.at> (raw)
In-Reply-To: <83tvguq1q5.fsf@gnu.org>
> How about installing this on master? Just please mention in the
> comments the convoluted use case that caused the change in order, so
> that we don't forget.
The use case is by no means convoluted. Try 'y-or-n-p' with a single
line prompt that exceeds the minibuffer window width. No feedback is
visible which is IMO a quite dangerous effect. Missing a question is
bad.
Anyway. I doubt that installing my change without accompanying
measures will work out of the box. But first of all I'd like to know
whether your change was intentionally asymmetric (if so, why?),
experimentally asymmetric (which experiments did you conduct?), or
accidentally so (it's rather atypical of you to install asymmetric
behavior and not document it).
And obviously, all this evil has two roots: The fact that redisplay
may call 'select-frame' and the one that do_switch_frame always
shrinks the minibuffer window of the frame it leaves. Together these
make debugging resize_mini_window calls a nightmare.
martin
next prev parent reply other threads:[~2019-02-23 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 18:49 bug#34317: 26.1.90; Wrong unbinding order in x_consider_frame_title martin rudalics
2019-02-19 9:07 ` martin rudalics
2019-02-23 9:43 ` Eli Zaretskii
2019-02-23 14:00 ` martin rudalics [this message]
2019-02-23 16:46 ` Eli Zaretskii
2019-02-24 8:43 ` martin rudalics
2019-02-24 16:08 ` Eli Zaretskii
2019-02-24 18:30 ` martin rudalics
2019-02-24 18:57 ` Eli Zaretskii
2019-03-04 10:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C7151FF.5070504@gmx.at \
--to=rudalics@gmx.at \
--cc=34317@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.