From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Allowing point to be outside the window?
Date: Sun, 06 Feb 2022 18:15:38 +0200 [thread overview]
Message-ID: <8335kwynrp.fsf@gnu.org> (raw)
In-Reply-To: <87pmo0mbig.fsf@yahoo.com> (message from Po Lu on Sun, 06 Feb 2022 20:21:11 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 06 Feb 2022 20:21:11 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Since scrolling is basically implemented in redisplay, I don't think
> > this answers my question.
> >
> > Let's look at this from another aspect: which combinations of values
> > of these two variables make sense, and what would be the behavior
> > under each one of these reasonable combinations?
>
> It makes sense to have `scroll-move-point' to t, and
> `keep-point-visible' set to nil or t, and `scroll-move-point' set to nil
> when `keep-point-visible' is nil.
>
> The behaviour under the first and combinations would be that scrolling
> moves point to fit inside the visible portion of the buffer. With the
> third, scrolling will not move the point at all.
So we have at most 3 states, and could have a single tri-state
variable.
And I question the validity of the combination scroll-move-point = nil
with keep-point-visible = t. The problem with your implementation is
that scroll-move-point = nil disables scrolling in redisplay_window,
but scrolling there is used not necessarily as result of scrolling
commands, but also when redisplay_window decides that the optimal
method of updating a window is to scroll its previous contents. Thus,
disabling scrolling on that level will cause confusing results,
because users will expect that to affect only scrolling commands: they
are unaware that redisplay sometimes scrolls the window for other
reasons.
> >> >> @@ -5659,8 +5660,9 @@ window_scroll_pixel_based (Lisp_Object window, int n, bool whole, bool noerror)
> >> >> w->start_at_line_beg = true;
> >> >> wset_update_mode_line (w);
> >> >> /* Set force_start so that redisplay_window will run the
> >> >> - window-scroll-functions. */
> >> >> - w->force_start = true;
> >> >> + window-scroll-functions, unless scroll_move_point is false,
> >> >> + in which case forcing the start will cause recentering. */
> >> >> + w->force_start = scroll_move_point;
>
> > That doesn't really answer my question. I was asking what is the
> > semantics of setting the window-start, but not the force_start flag?
> > What is expected from redisplay in this case? should it obey
> > window-start?
>
> It's expected that it will obey window-start (unless some text changed
> before it, in which case it will recenter around the first change
> position.)
For that, you must set the force_start flag. If you don't set it,
redisplay cannot know whether the value of w->start is just the result
of the previous redisplay cycle or was set by some user command which
wants to scroll the window.
Perhaps you want to explore using w->optional_new_start instead?
> > No, I mean don't we want to force point to move to the locus of these
> > changes? I thought other applications did that.
>
> They provide no way to make changes without point already being at the
> locus of the change. (In which case it will be caught either by the `PT
> != w->last_point' conditional, and redisplay will recenter around point
> as usual, or if point did not move, then it will recenter around the
> change, which would be near the point in that case.)
>
> IOW, there's no way in most other editors to do something like this:
>
> (save-excursion
> (goto-char (point-min))
> (insert "foo"))
Maybe so should we, at least as an option.
next prev parent reply other threads:[~2022-02-06 16:15 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ilwd7zaq.fsf.ref@yahoo.com>
2021-11-28 3:07 ` Allowing point to be outside the window? Po Lu
2021-11-28 8:03 ` Eli Zaretskii
2021-11-28 8:13 ` Po Lu
2021-11-28 8:41 ` Eli Zaretskii
2021-11-28 12:47 ` Po Lu
2021-11-28 12:58 ` Eli Zaretskii
2021-11-28 13:10 ` Po Lu
2021-11-28 13:44 ` Eli Zaretskii
2021-11-29 1:47 ` Po Lu
2021-11-29 13:00 ` Eli Zaretskii
2021-11-29 13:22 ` Po Lu
2021-11-29 13:43 ` Eli Zaretskii
2021-11-30 1:40 ` Po Lu
2021-11-30 16:49 ` [External] : " Drew Adams
2021-11-30 17:26 ` Eli Zaretskii
2021-11-30 18:10 ` Lars Ingebrigtsen
2021-11-30 18:32 ` Eli Zaretskii
2021-11-30 18:49 ` Stefan Kangas
2021-11-30 19:21 ` Eli Zaretskii
2021-11-30 20:57 ` Drew Adams
2021-11-30 23:41 ` Daniel Martín
2021-12-01 8:30 ` martin rudalics
2021-12-01 9:10 ` Juri Linkov
2021-11-30 23:20 ` Stefan Monnier
2021-12-04 11:18 ` Po Lu
2021-12-04 12:55 ` Eli Zaretskii
2021-12-04 13:13 ` Po Lu
2021-12-04 16:24 ` Eli Zaretskii
2021-12-05 0:40 ` Po Lu
2021-12-04 17:15 ` Eli Zaretskii
2021-12-05 0:45 ` Po Lu
2021-12-05 9:03 ` Eli Zaretskii
2021-12-06 2:11 ` Po Lu
2021-12-06 14:13 ` Eli Zaretskii
2021-12-07 2:18 ` Po Lu
2021-12-07 13:42 ` Eli Zaretskii
2021-12-08 1:17 ` Po Lu
2021-12-08 17:14 ` Eli Zaretskii
2021-12-09 0:23 ` Po Lu
2021-12-09 8:02 ` Eli Zaretskii
2021-12-09 9:22 ` Po Lu
2021-12-09 10:02 ` Eli Zaretskii
2021-12-25 6:45 ` Po Lu
2021-12-25 7:07 ` Eli Zaretskii
2022-02-06 7:22 ` Po Lu
2022-02-06 11:34 ` Eli Zaretskii
2022-02-06 11:46 ` Po Lu
2022-02-06 11:55 ` Eli Zaretskii
2022-02-06 12:21 ` Po Lu
2022-02-06 16:15 ` Eli Zaretskii [this message]
2022-02-07 1:21 ` Po Lu
2022-02-07 7:21 ` Po Lu
2022-02-07 13:41 ` Eli Zaretskii
2022-02-07 13:57 ` Po Lu
2022-02-07 14:24 ` Eli Zaretskii
2022-02-08 0:58 ` Po Lu
2022-02-08 17:08 ` Eli Zaretskii
2022-02-09 1:57 ` Po Lu
2022-02-10 13:04 ` Eli Zaretskii
2022-02-10 13:09 ` Po Lu
2021-12-09 11:45 ` Eli Zaretskii
2021-12-09 12:19 ` Po Lu
2021-12-09 12:45 ` Eli Zaretskii
2021-12-04 13:00 ` dick
2021-12-04 13:14 ` tomas
2021-12-04 13:19 ` Po Lu
2021-12-04 13:41 ` Eli Zaretskii
2021-12-05 0:46 ` Po Lu
2021-12-05 7:12 ` Eli Zaretskii
2021-12-05 7:16 ` Po Lu
2021-12-05 8:48 ` Eli Zaretskii
2021-12-05 9:15 ` Po Lu
2021-12-05 9:25 ` Eli Zaretskii
2021-12-05 9:31 ` Po Lu
2021-12-05 10:34 ` Eli Zaretskii
2021-12-05 10:37 ` Po Lu
2021-12-04 14:17 ` dick
2021-12-04 16:33 ` Eli Zaretskii
2021-12-04 17:13 ` dick
2021-12-05 0:48 ` Po Lu
2021-11-28 14:03 ` Alan Mackenzie
2021-11-28 14:28 ` Eric S Fraga
2021-11-28 14:39 ` Eli Zaretskii
2021-11-28 16:55 ` Eric S Fraga
2021-11-28 14:42 ` dick
2021-11-28 15:39 ` Kévin Le Gouguec
2021-11-28 15:45 ` Eli Zaretskii
2021-11-28 17:14 ` Kévin Le Gouguec
2021-11-28 16:59 ` Eric S Fraga
2021-11-28 17:30 ` Kévin Le Gouguec
2021-11-29 0:34 ` Dmitry Gutov
2021-11-29 0:34 ` Po Lu
2021-12-08 1:45 ` John Ankarström
2021-12-08 12:45 ` Eli Zaretskii
2021-12-08 13:33 ` John Ankarström
2021-12-08 13:38 ` Po Lu
2021-12-08 13:52 ` John Ankarström
2021-12-08 14:26 ` Eli Zaretskii
2021-12-08 16:57 ` Stefan Monnier
2021-12-08 19:29 ` Yuri Khan
2021-12-09 0:16 ` Po Lu
2021-12-08 19:21 ` Rudolf Schlatte
2021-12-08 19:56 ` Juri Linkov
2021-12-08 20:05 ` André A. Gomes
2021-12-08 20:31 ` Linux console scrollback [ Was: Allowing point to be outside the window? ] Alan Mackenzie
2021-12-09 0:17 ` Allowing point to be outside the window? Po Lu
2021-12-08 22:25 ` Kévin Le Gouguec
2021-12-08 23:17 ` John Ankarström
[not found] <9603C99D-97E7-4285-A1C1-022191B6F5CC@univie.ac.at>
2021-12-08 18:43 ` Konrad Podczeck
2021-12-08 20:47 ` John Ankarström
2021-12-09 15:34 Konrad Podczeck
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=8335kwynrp.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).