all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Al Petrofsky <al@petrofsky.org>
Cc: 64139@debbugs.gnu.org, juri@linkov.net
Subject: bug#64139: 28.2; Scrolling problems in miniwindow
Date: Wed, 21 Jun 2023 18:01:27 +0300	[thread overview]
Message-ID: <83jzvw506w.fsf@gnu.org> (raw)
In-Reply-To: <CAPMQwz7Ek5BTZoiu6iXy+nt==h8arQ7bSJ-eC+2BRa=W54_iFA@mail.gmail.com> (message from Al Petrofsky on Mon, 19 Jun 2023 18:33:38 -0400)

> From: Al Petrofsky <al@petrofsky.org>
> Date: Mon, 19 Jun 2023 18:33:38 -0400
> Cc: Juri Linkov <juri@linkov.net>, 64139@debbugs.gnu.org
> 
> Here's a simpler and clearer recipe that should show the problem on
> any tty or X display:
> 
>    emacs-28.2 -Q
>    M-: C-u 9 9 C-q C-j x C-@ M-< C-v
> 
> This creates a 100-line minibuffer with "x" on the last line.  After
> the M-< and C-v, we should be one windowful down from the top, but
> instead we've scrolled nearly to the end and the "x" has shown up on
> the last line.

Thanks.

This is a feature: scrolling (and redisplay in general) in the
mini-window is tailored to try and display the most important part of
the minibuffer text.  The feature is intended to support various
minibuffer-editing packages which display a lot of text in the
mini-window when the user is prompted for a file name or other similar
stuff, of which there are a lot of possible candidates.

If you set the variable redisplay-adhoc-scroll-in-resize-mini-windows
to a nil value, you will get the "normal" scrolling behavior in the
mini-window.





  reply	other threads:[~2023-06-21 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18  0:26 bug#64139: 28.2; Scrolling problems in miniwindow Al Petrofsky
2023-06-18  7:09 ` Eli Zaretskii
2023-06-18  9:07   ` Al Petrofsky
2023-06-19 22:33     ` Al Petrofsky
2023-06-21 15:01       ` Eli Zaretskii [this message]
2023-06-19 17:20   ` Juri Linkov

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=83jzvw506w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64139@debbugs.gnu.org \
    --cc=al@petrofsky.org \
    --cc=juri@linkov.net \
    /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.