From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32839@debbugs.gnu.org
Subject: bug#32839: 27.0.50; recenter doesn't redisplay
Date: Thu, 27 Sep 2018 02:55:38 +0300 [thread overview]
Message-ID: <87tvmbq2pp.fsf@mail.linkov.net> (raw)
In-Reply-To: <83k1n895qv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Sep 2018 08:39:52 +0300")
> Also, you are talking about 2 different functions -- 'recenter' and
> 'recenter-top-bottom' -- and that adds confusion to the discussion, so
> maybe I misunderstood something you wanted to say.
I wanted to say that I see two problems here:
1. recenter doesn't redraw the frame when it is called with
a non-nil REDISPLAY argument.
In `recenter-top-bottom', when `recenter-last-op' is `top',
this gets called:
(recenter this-scroll-margin t)
When `this-scroll-margin' is 0, the actual call is:
(recenter 0 t)
Despite its REDISPLAY argument set to t, the frame is not redisplayed.
2. The second problem is that after the call to (recenter -1 t),
window-scroll-functions is called only when recenter moves the current
buffer line to the second-last window line (when the last window line is
partially visible). But when the last window line is fully visible,
window-scroll-functions is not called after (recenter -1 t).
next prev parent reply other threads:[~2018-09-26 23:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:11 bug#32839: 27.0.50; recenter doesn't redisplay Juri Linkov
2018-09-25 20:08 ` Eli Zaretskii
2018-09-25 20:55 ` Juri Linkov
2018-09-26 5:39 ` Eli Zaretskii
2018-09-26 23:55 ` Juri Linkov [this message]
2018-09-27 6:44 ` Eli Zaretskii
2018-09-27 22:59 ` Juri Linkov
2018-09-28 6:22 ` Eli Zaretskii
2018-09-29 23:32 ` Juri Linkov
2018-09-30 6:08 ` Eli Zaretskii
2018-09-30 19:40 ` Juri Linkov
2018-10-01 5:34 ` Eli Zaretskii
2018-09-29 23:38 ` Juri Linkov
2018-09-30 6:22 ` Eli Zaretskii
2018-09-30 19:46 ` Juri Linkov
2018-10-01 6:58 ` Eli Zaretskii
2018-10-08 22:56 ` Juri Linkov
2018-10-09 7:44 ` martin rudalics
2020-02-07 0:30 ` Juri Linkov
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=87tvmbq2pp.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=32839@debbugs.gnu.org \
--cc=eliz@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.
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).