From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: 32672@debbugs.gnu.org
Subject: bug#32672: 27.0.50; image resize on window resizing
Date: Tue, 25 Sep 2018 09:27:39 +0200 [thread overview]
Message-ID: <5BA9E36B.8040300@gmx.at> (raw)
In-Reply-To: <87d0t3gicm.fsf@mail.linkov.net>
> Maybe because taking out window size change notifications from
> window-configuration-change-hook is a backward-incompatible change?
Certainly so. But we now have the situation that only parts of the
size changes are reflected in calls of
'window-configuration-change-hook'. I almost certainly will reinstate
the call for frame size changes because of Bug#32720. But I won't
cover minibuffer window induced size changes. Apparently there's no
harm in that because most callers of
'window-configuration-change-hook' are only interested in changes of
window widths (and as such will be affected when the body width of a
window changes with its total width unchanged).
>>> and window-scroll-functions (also called too often).
>>
>>> Regarding window-scroll-functions, it would be too strange to use
>>> it to catch set-window-buffer calls.
>>>
>>> (info "(elisp) Window Hooks") says:
>>>
>>> There are three actions that can change this: scrolling the window,
>>> switching buffers in the window, and changing the size of the window.
>>> The first two actions run ‘window-scroll-functions’; the last runs
>>> ‘window-size-change-functions’.
>>>
>>> Shouldn't the first two actions run separate hooks?
>
> Please also answer this question. I believe this is the crucial question
> for this request.
I have no answer to this question. But note that switching buffers
also runs 'window-configuration-change-hook'. The latter is not run
when just the start position of that window's buffer changes.
> Sorry, actually it works, I missed the logged messages because the content
> of the *Messages* buffer is not refreshed to show new logged messages
> from the calls of the window-scroll-functions hook such as
>
> (add-to-list 'window-scroll-functions
> (lambda (window display-start)
> (message "window-scroll-functions %S %S %S"
> window (window-buffer window) display-start)))
>
> 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.
> Only after switching to the *Messages* buffer with 'C-x o' it gets
> redisplayed and all previously emitted messages appear in it.
I never recenter so I have no idea what to expect from that function.
But from the doc I assume that you have to set 'recenter-redisplay'
appropriately.
martin
next prev parent reply other threads:[~2018-09-25 7:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 15:54 bug#32672: 27.0.50; image resize on window resizing Juri Linkov
2018-09-11 23:53 ` Juri Linkov
2018-09-12 6:33 ` martin rudalics
2018-09-12 23:18 ` Juri Linkov
2018-09-13 7:46 ` martin rudalics
2018-09-13 23:20 ` Juri Linkov
2018-09-14 8:33 ` martin rudalics
2018-09-15 23:35 ` Juri Linkov
2018-09-16 9:10 ` martin rudalics
2018-09-16 23:49 ` Juri Linkov
2018-09-17 6:46 ` martin rudalics
2018-09-17 22:35 ` Juri Linkov
2018-09-19 8:22 ` martin rudalics
2018-09-19 23:15 ` Juri Linkov
2018-09-20 7:34 ` martin rudalics
2018-09-20 23:15 ` Juri Linkov
2018-09-21 6:34 ` martin rudalics
2018-09-22 22:15 ` Juri Linkov
2018-09-23 8:26 ` martin rudalics
2018-09-23 20:39 ` Juri Linkov
2018-09-24 8:22 ` martin rudalics
2018-09-24 8:35 ` Eli Zaretskii
2018-09-24 12:25 ` martin rudalics
2018-09-24 12:46 ` Eli Zaretskii
2018-09-24 17:37 ` martin rudalics
2018-09-24 17:53 ` Eli Zaretskii
2018-09-25 7:26 ` martin rudalics
2018-09-25 9:19 ` Eli Zaretskii
2018-09-25 17:56 ` martin rudalics
2018-09-25 18:31 ` Eli Zaretskii
2018-09-24 18:38 ` Juri Linkov
2018-09-24 19:31 ` Eli Zaretskii
2018-09-25 7:27 ` martin rudalics
2018-09-25 19:24 ` Juri Linkov
2018-09-26 8:51 ` martin rudalics
2018-10-27 19:38 ` Juri Linkov
2018-10-28 8:59 ` martin rudalics
2018-09-24 18:31 ` Juri Linkov
2018-09-25 7:27 ` martin rudalics [this message]
2018-12-26 23:42 ` Juri Linkov
2018-12-27 9:36 ` martin rudalics
2018-12-27 21:41 ` Juri Linkov
2018-12-28 8:34 ` martin rudalics
2018-12-27 15:48 ` Eli Zaretskii
2018-12-27 20:58 ` Juri Linkov
2018-12-28 4:51 ` Eli Zaretskii
2019-09-26 13:27 ` Lars Ingebrigtsen
2019-11-27 21:53 ` Juri Linkov
2019-11-28 9:20 ` martin rudalics
2019-11-28 22:50 ` Juri Linkov
2019-11-29 9:24 ` martin rudalics
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=5BA9E36B.8040300@gmx.at \
--to=rudalics@gmx.at \
--cc=32672@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).