From: Spencer Williams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66773@debbugs.gnu.org
Subject: bug#66773: 29.1; Ido displays incorrectly with multiple frames when ido-max-window-height=1
Date: Sat, 28 Oct 2023 19:41:45 -0400 [thread overview]
Message-ID: <m24jiagvm4.fsf@plexwave.org> (raw)
In-Reply-To: <83ttqbcg0s.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> But in that case, the result of Git bisection is incorrect, since
> reverting that commit doesn't change the behavior in this recipe, at
> least on my system. Did you see any change in behavior when you
> reverted the commit to which "git bisect" pointed?
There is no change when reverting it against Emacs 29 or master. I
apologize for not mentioning this before. There is a change, however,
when reverting against the commit's immediate parent; so, coincidentally
or otherwise, the commit does manifest the behavior I've demonstrated. I
cannot speak to the ramifications for the rest of the codebase (I
understand much has likely changed in the two years since that commit
was made).
> The reason for what you see is the new handling of mini-windows
> introduced in Emacs 28 (not in 29), whereby by default we show the end
> of the mini-buffer text, not its beginning.
That is certainly interesting, as I can affirm this behavior was not
present in any version of Emacs 28 I've tested (up to emacs-28.3-rc1).
> It looks to me that when ido-max-window-height is set to 1, the
> variable redisplay-adhoc-scroll-in-resize-mini-windows should be set
> to the nil value, which will make the behavior in your recipe
> consistent, at least in my testing.
It does, and I thank you much for turning me onto that, as it at least
provides a usable fix for now.
next prev parent reply other threads:[~2023-10-28 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 20:15 bug#66773: 29.1; Ido displays incorrectly with multiple frames when ido-max-window-height=1 Spencer Williams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27 10:49 ` Eli Zaretskii
2023-10-27 22:47 ` Spencer Williams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28 8:22 ` Eli Zaretskii
2023-10-28 23:41 ` Spencer Williams via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-18 8:34 ` Eli Zaretskii
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=m24jiagvm4.fsf@plexwave.org \
--to=bug-gnu-emacs@gnu.org \
--cc=66773@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=spnw@plexwave.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).