all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 27 Oct 2023 18:47:40 -0400	[thread overview]
Message-ID: <m28r7nhe6p.fsf@plexwave.org> (raw)
In-Reply-To: <83leboe3vv.fsf@gnu.org>


Eli Zaretskii <eliz@gnu.org> writes:

> 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.

I consider it a bug due to inconsistent behavior. With multiple
frames, the behavior is different than it is with only one frame.

> 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.

In Ido's case it is certainly incorrect to show the end first, due to
the prompt and selection being at the beginning. My concern is that in
Emacs 28 it had no trouble, and in Emacs 29 it acts erratically.

> The change to which you point affect general Emacs behavior, it
> isn't specific to ido-mode.

I understand that. I originally meant for this report to be more
general, as I did believe Emacs's drawing code to be at fault, but in
the end Ido was the only definitive example of wrong behavior I could
reproduce. I included the commit reference on the outside chance it
might save someone some digging (as I'd already put a little work into
finding a solution myself).

I hope that if it is indeed an Ido-specific bug, this report will still
be of some use. Thanks for your time.





  reply	other threads:[~2023-10-27 22:47 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 [this message]
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=m28r7nhe6p.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 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.