From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Redisplay resets vscroll when window start changes
Date: Tue, 16 Nov 2021 15:45:18 +0200 [thread overview]
Message-ID: <83mtm41afl.fsf@gnu.org> (raw)
In-Reply-To: <87zgq4te32.fsf@yahoo.com> (message from Po Lu on Tue, 16 Nov 2021 21:38:57 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 16 Nov 2021 21:38:57 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > If you are moving to another line, how would it make sense to leave
> > vscroll alone? Or what am I missing?
>
> Basically, if someone has the following content in a window:
>
> AAAA
> BBBB
> CCCC
> DDDD
> EEEE
> FFFF
> GGGG
> HHHH
>
> And point is on the first "G", while vscroll is set so that part of
> "AAAA" is obscured, he will expect moving up so that point is on the
> first "F" to not reset the vscroll.
Moving up pixelwise? that should gradually show more and more of AAAA
with each pixel movement. How is vscroll involved here?
Or are you talking about some other kind of "moving up?
next prev parent reply other threads:[~2021-11-16 13:45 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 [this message]
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
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=83mtm41afl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).