From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 32637@debbugs.gnu.org
Subject: bug#32637: 27.0.50; window-size-change-functions not run from local hook
Date: Thu, 06 Sep 2018 05:35:20 +0300 [thread overview]
Message-ID: <837ejzxsif.fsf@gnu.org> (raw)
In-Reply-To: <87a7ov1ucp.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 06 Sep 2018 00:56:38 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: martin rudalics <rudalics@gmx.at>, 32637@debbugs.gnu.org
> Date: Thu, 06 Sep 2018 00:56:38 +0300
>
> > I actually don't understand why we need to support buffer-local hooks
> > in window-size-change-functions. This hook clearly applies to the
> > entire frame, so anything buffer-local sounds inappropriate there.
>
> A buffer-local hook is useful when a mode needs to reformat its
> buffer content on window resizing.
We have no control on what each hook could or could not do. We give
programmers a rope, but cannot prevent them from hanging themselves
(and take down Emacs with them).
E.g., what happens if two buffers displayed on the same frame have
different hooks there, which just happen to have conflicting ideas of
what should be done when windows are resized? How will they be able
to reconcile their conflict?
Makes very little sense to me.
next prev parent reply other threads:[~2018-09-06 2:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 21:03 bug#32637: 27.0.50; window-size-change-functions not run from local hook Juri Linkov
2018-09-05 7:47 ` martin rudalics
2018-09-05 15:26 ` Eli Zaretskii
2018-09-05 21:56 ` Juri Linkov
2018-09-06 2:35 ` Eli Zaretskii [this message]
2018-09-06 22:17 ` Juri Linkov
2018-09-05 21:54 ` Juri Linkov
2018-09-06 7:05 ` martin rudalics
2018-09-06 22:06 ` Juri Linkov
2018-09-07 7:31 ` martin rudalics
2018-09-08 23:56 ` Juri Linkov
2018-09-09 6:03 ` Eli Zaretskii
2018-09-09 8:40 ` martin rudalics
2018-09-09 15:59 ` Eli Zaretskii
2018-09-10 8:29 ` martin rudalics
2018-09-09 16:17 ` Juri Linkov
2018-09-10 8:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837ejzxsif.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32637@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.