unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55312@debbugs.gnu.org
Subject: bug#55312: 29.0.50; Cannot set vscroll when mini-window is resized
Date: Sun, 08 May 2022 16:40:59 +0300	[thread overview]
Message-ID: <83y1zcuopg.fsf@gnu.org> (raw)
In-Reply-To: <877d6w44wp.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)

> Date: Sun, 08 May 2022 19:53:10 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> It seems that this code in redisplay_window always clears out the
> vscroll when the mini-window is taller than a single line of text:

Not when it's taller, but when it has been resized.

> This can easily be reproduced by typing "M-x C-q C-j" and trying to use
> `pixel-scroll-precision' with the mouse pointer on top of a window that
> is not the `minibuf-scroll-window': the vscroll will not take effect,
> since force_start will be set to true, and that resets the vscroll.
> 
> I think this "frozen" behavior is required to ensure that the start of
> windows do not aimlessly move when the mini-window is being resized, but
> it interferes with features that need to set the vscroll.
> 
> Any ideas?

If you want to allow vscroll in these cases, you'd need to either add
code which ensures the window-start of "frozen" windows is not moved
by means other than the force_start flag, or modify the code where we
handle the force_start flag so that it doesn't reset vscroll when
pixel-scroll uses it, as opposed to when vscroll is used by "normal"
scrolling commands for the purposes of scrolling tall screen lines.





  reply	other threads:[~2022-05-08 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877d6w44wp.fsf.ref@yahoo.com>
2022-05-08 11:53 ` bug#55312: 29.0.50; Cannot set vscroll when mini-window is resized Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 13:40   ` Eli Zaretskii [this message]
2022-05-09  0:29     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-09  1:38       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-09 13:48         ` Eli Zaretskii
2022-05-10  0:43           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83y1zcuopg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55312@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /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).