unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com,  mwd@md5i.com,  emacs-devel@gnu.org
Subject: Re: Redisplay resets vscroll when window start changes
Date: Thu, 18 Nov 2021 22:17:41 -0500	[thread overview]
Message-ID: <jwvee7c4yzw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83zgq2x95p.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Nov 2021 08:36:18 +0200")

>> >> Would there be a way to distinguish the case where line-move can return
>> >> a correct result without changing vscroll, from the case where it does
>> >> require changing vscroll in order to find its answer?
>> > I don't think I understand the question.
>> 
>> The question can be rephrased as: could `line-move` only reset vscroll
>> in the case where we're scrolling through a very tall image?
>
> It currently handles the case of a tall screen line, which could be
> due to an image, an xwidget, or simply very large font.
>
> If you want to limit it only to those cases, then perhaps the answer
> is yes, but the problem with those functions is that they try to
> handle many use cases that are not completely described anywhere, so
> testing whether a particular change could break any of them is nigh
> impossible in practice.  And the code does work for the use cases for
> which it was written.  Which is why I suggested a completely new
> command for the purpose under discussion.

I must be missing something: in the test case posted here, AFAICT we
just have a call to `previous-line` which doesn't involve any tall
screen line, yet the result is still that vscroll is reset.


        Stefan




  reply	other threads:[~2021-11-19  3:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k0h9pp7t.fsf.ref@yahoo.com>
2021-11-15 12:39 ` Redisplay resets vscroll when window start changes Po Lu
2021-11-15 12:44   ` Po Lu
2021-11-15 14:18   ` Eli Zaretskii
2021-11-16  0:02     ` Po Lu
2021-11-16 12:51       ` Eli Zaretskii
2021-11-16 12:54         ` Po Lu
2021-11-16 13:01           ` Po Lu
2021-11-16 13:34             ` Eli Zaretskii
2021-11-16 13:38               ` Po Lu
2021-11-16 13:45                 ` Eli Zaretskii
2021-11-16 17:12                   ` Michael Welsh Duggan
2021-11-16 18:31                     ` Eli Zaretskii
2021-11-17  3:24                       ` Stefan Monnier
2021-11-17 13:34                         ` Eli Zaretskii
2021-11-17  0:26                     ` Po Lu
2021-11-17  3:31                       ` Eli Zaretskii
2021-11-17  3:40                         ` Stefan Monnier
2021-11-17 13:40                           ` Eli Zaretskii
2021-11-17 20:40                             ` Stefan Monnier
2021-11-18  6:36                               ` Eli Zaretskii
2021-11-19  3:17                                 ` Stefan Monnier [this message]
2021-11-19  7:13                                   ` Eli Zaretskii
2021-11-19 18:07                                     ` Stefan Monnier
2021-11-19 18:43                                       ` Eli Zaretskii
2021-11-17  4:31                         ` Po Lu
2021-11-17  7:45                           ` Eli Zaretskii
2021-11-17  0:21                   ` Po Lu

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=jwvee7c4yzw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=mwd@md5i.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).