Re: Allowing point to be outside the window?

[Po Lu]

Po Lu <luangruo@yahoo.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> So we have at most 3 states, and could have a single tri-state
>> variable.
>
> Indeed.
>
>> 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.
>
> Perhaps we could have redisplay bind `scroll-move-point' to a reasonable
> value before calling the scrolling commands?

I don't see where the scrolling commands in window.c get called from
`redisplay_window'.  Is it try_scrolling?  If so, I see nothing there.

Thanks.