From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 22637@debbugs.gnu.org
Subject: bug#22637: 25.1.50; `mode-line` face `:height` incompatible with `scroll-conservatively 101`.
Date: Tue, 16 Feb 2016 17:51:28 +0200 [thread overview]
Message-ID: <83oabgwt4v.fsf@gnu.org> (raw)
In-Reply-To: <m2io1pfjv5.wl%esq@lawlist.com> (message from Keith David Bershatsky on Mon, 15 Feb 2016 18:51:26 -0800)
> Date: Mon, 15 Feb 2016 18:51:26 -0800
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: 22637@debbugs.gnu.org
>
> The same situation mentioned in my email earlier today (02/15/2016) is also present in the first test case that we looked at for #22637. I.e., after an insertion in the first test case, the `window-scroll-functions` hook never fires after `window-start` is corrected. So a user seeking to use the `window-scroll-functions` hook following a large insertion (e.g., a large yank, and so forth) is out of luck in that situation in terms of using a correct `window-start`. I have already dealt with it for the `window-start-end-hook` by forcing a call every command loop thereby bypassing "optimization 3"; however, the WSF has no fix at this time.
The reason window-scroll-functions aren't run in both of these test
cases is that what happens there is not considered "scrolling".
Scrolling is informally defined as either an explicit call to a
function that scrolls the window, or a pseudo-scroll done by the
display engine when it detects that some part of the window's previous
display is still present, but in a different vertical position.
Moving point to an arbitrary location is neither.
next prev parent reply other threads:[~2016-02-16 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 2:12 bug#22637: 25.1.50; `mode-line` face `:height` incompatible with `scroll-conservatively 101` Keith David Bershatsky
2016-02-12 8:17 ` Eli Zaretskii
2016-02-12 16:17 ` Keith David Bershatsky
2016-02-12 19:40 ` Eli Zaretskii
2016-02-14 3:40 ` Keith David Bershatsky
2016-02-14 6:05 ` Eli Zaretskii
2016-02-14 7:55 ` Keith David Bershatsky
2016-02-14 19:26 ` Eli Zaretskii
2016-02-16 2:00 ` Keith David Bershatsky
2016-02-16 2:51 ` Keith David Bershatsky
2016-02-16 15:51 ` Eli Zaretskii [this message]
2022-02-10 8:09 ` Lars Ingebrigtsen
2022-02-10 12:33 ` Eli Zaretskii
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=83oabgwt4v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22637@debbugs.gnu.org \
--cc=esq@lawlist.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).