unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 32839@debbugs.gnu.org
Subject: bug#32839: 27.0.50; recenter doesn't redisplay
Date: Tue, 25 Sep 2018 23:08:04 +0300	[thread overview]
Message-ID: <83lg7p8hnf.fsf@gnu.org> (raw)
In-Reply-To: <8736txjvkg.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 25 Sep 2018 22:11:59 +0300)

> From: Juri Linkov <juri@linkov.net>
> Date: Tue, 25 Sep 2018 22:11:59 +0300
> 
> 1. Eval:
> 
> (setq recenter-redisplay t)
> 
> (add-to-list 'window-scroll-functions
>              (lambda (window display-start)
>                (message "window-scroll-functions %S %S %S"
>                         window (window-buffer window) display-start)))
> 
> 2. Open *Messages* in adjacent window with 'C-h e'
> 
> 3. Put point in *scratch* preferably not on the first line
> 
> 4. Type 'C-l' (recenter-top-bottom) with different arguments, e.g.
>    C-0 C-l
>    C-1 C-l
>    C-2 C-l
>    etc.
> 
> The *Messages* buffer is not refreshed to show new logged messages
> from the calls of the window-scroll-functions.
> 
> This means that C-l (recenter-top-bottom) doesn't redisplay the frame -
> which is strange since it calls 'recenter' with non-nil arg REDISPLAY.

'recenter' doesn't redisplay the frame, it only redisplays the window
which you recenter.

> 5. Typein *scratch* again: C-l C-l C-l
>    only when C-l puts point to the center of the window,
>    the *Messages* buffer gets redisplayed (but then for some reason
>    window-scroll-functions is not called in this case).

That's a feature: you set recenter-redisplay to t, which causes a
complete redraw of the frame when you type C-l.  And
window-scroll-functions aren't called when the window is not scrolled.

Bottom line: I'm unsure what is a bug here, if any.





  reply	other threads:[~2018-09-25 20:08 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 [this message]
2018-09-25 20:55   ` Juri Linkov
2018-09-26  5:39     ` Eli Zaretskii
2018-09-26 23:55       ` Juri Linkov
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=83lg7p8hnf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32839@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).