From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Williams <spnw@plexwave.org>
Cc: 66773@debbugs.gnu.org
Subject: bug#66773: 29.1; Ido displays incorrectly with multiple frames when ido-max-window-height=1
Date: Fri, 27 Oct 2023 13:49:56 +0300 [thread overview]
Message-ID: <83leboe3vv.fsf@gnu.org> (raw)
In-Reply-To: <m234xx5ees.fsf@plexwave.org> (bug-gnu-emacs@gnu.org)
> Date: Thu, 26 Oct 2023 16:15:07 -0400
> From: Spencer Williams via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> When using multiple graphical frames, setting ido-max-window-height to 1
> only works as expected on the initial frame. On all other frames,
> supposing the minibuffer length is great enough, the beginning will be
> occluded until user input is received.
>
> This can be easily demonstrated by running the following code on a fresh
> graphical Emacs, and then pressing C-x b to switch buffers:
>
> (progn
> (ido-mode 1)
> (setq ido-max-window-height 1)
> (dotimes (i 100)
> (generate-new-buffer "foobar"))
> (make-frame))
>
> The bug manifests on both Linux and macOS (vanilla builds). It was not
> present on Emacs 28. I ran a git-bisect and the "first bad commit"
> appears to be c0b9041ebde82907711cc00a7c307fe622fb541c.
If the minibuffer text is longer than what the mini-window can show,
then it is not clear whether Emacs should show the beginning or the
end of the minibuffer text. So I don't see how this is a bug and why
would the alternative behavior be better. Also, if you just type C-b,
you will see the rest of the buffer text.
If, for some reason, ido-mode wants to always display the beginning of
the minibuffer text, it can do that with a change specific to
ido-mode. The change to which you point affect general Emacs
behavior, it isn't specific to ido-mode.
next prev parent reply other threads:[~2023-10-27 10:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83leboe3vv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66773@debbugs.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 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.