From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Make scroll-{up, down} move point to {start, end} of newly visible text
Date: Thu, 24 Aug 2023 07:43:15 +0300 [thread overview]
Message-ID: <83r0ntqcd8.fsf@gnu.org> (raw)
In-Reply-To: <871qfu986m.fsf@dataswamp.org> (message from Emanuel Berg on Tue, 22 Aug 2023 21:41:05 +0200)
> From: Emanuel Berg <incal@dataswamp.org>
> Date: Tue, 22 Aug 2023 21:41:05 +0200
>
> Eli Zaretskii wrote:
>
> >> No, for example, by opening this very buffer, Emacs already
> >> knows its state, since it displays "All" in the mode bar (and
> >> I didn't scroll).
> >>
> >> So it is already there. Somewhere!
> >
> > Yes, but _after_ the display, not before.
>
> It is available before scrolling, like now it says 4%.
> The next time I execute a scroll function by hitting a key,
> that function could look at that data and use it to determine
> if scrolling should take place, and only then do it.
You once again lost the context. Your proposed solution required to
have this information _after_ the scroll command, to know where the
display will end up after performing the scrolling. For that purpose,
it is not very useful to know where you are _before_ scrolling.
> Just now I'm scrolling some more, and now it says "Bottom" in
> the mode bar instead. I am able to scroll more, but the
> function I describe would in this, changed situation see that
> it already is at the bottom and therefore not scroll.
These indications are updated after two things happen, one after the
other:
. the scroll command determines where to locate the window-start
position
. the following redisplay cycle actually scrolls the text to obey
what the scroll command determined, determines the window's end
position, and updates the mode-line indication like "Bottom"
Your proposed solution was to inject some logic _between_ those two,
and the position of the end of the window is not yet known at that
point.
next prev parent reply other threads:[~2023-08-24 4:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 20:18 Make scroll-{up, down} move point to {start, end} of newly visible text Spencer Baugh
2023-08-01 1:26 ` [External] : " Drew Adams
2023-08-01 11:44 ` hw
2023-08-01 5:11 ` Michael Heerdegen
2023-08-01 14:49 ` [External] : " Drew Adams
2023-08-01 11:28 ` hw
2023-08-01 14:45 ` Spencer Baugh
2023-08-01 16:05 ` hw
2023-08-01 12:42 ` Eli Zaretskii
2023-08-01 14:50 ` Spencer Baugh
2023-08-01 15:44 ` Eli Zaretskii
2023-08-01 18:09 ` Spencer Baugh
2023-08-01 18:35 ` Eli Zaretskii
2023-08-01 18:43 ` Spencer Baugh
2023-08-03 19:58 ` Spencer Baugh
2023-08-04 5:31 ` Eli Zaretskii
2023-08-06 20:02 ` Emanuel Berg
2023-08-08 12:41 ` Eli Zaretskii
2023-08-09 20:59 ` Emanuel Berg
2023-08-10 17:33 ` Eli Zaretskii
2023-08-10 18:06 ` Emanuel Berg
2023-08-11 11:30 ` Eli Zaretskii
2023-08-11 12:19 ` Emanuel Berg
2023-08-11 18:40 ` Eli Zaretskii
2023-08-11 19:00 ` Emanuel Berg
2023-08-12 13:30 ` Eli Zaretskii
2023-08-11 19:04 ` Emanuel Berg
2023-08-12 13:31 ` Eli Zaretskii
2023-08-12 15:35 ` Emanuel Berg
2023-08-13 13:23 ` Eli Zaretskii
2023-08-20 3:38 ` Emanuel Berg
2023-08-22 12:29 ` Eli Zaretskii
2023-08-22 19:41 ` Emanuel Berg
2023-08-24 4:43 ` Eli Zaretskii [this message]
2023-08-24 5:13 ` Emanuel Berg
2023-08-16 16:20 ` Spencer Baugh
2023-08-16 16:53 ` Eli Zaretskii
2023-08-16 17:55 ` Spencer Baugh
2023-08-16 18:33 ` Eli Zaretskii
2023-08-16 20:32 ` Spencer Baugh
2023-08-17 5:18 ` Eli Zaretskii
2023-08-17 12:19 ` Spencer Baugh
2023-08-17 12:30 ` Eli Zaretskii
2023-08-02 10:06 ` Emanuel Berg
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=83r0ntqcd8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).