From: martin rudalics <rudalics@gmx.at>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Wrong window end reported after splitting window
Date: Sat, 23 Feb 2008 23:36:42 +0100 [thread overview]
Message-ID: <47C09FFA.4040604@gmx.at> (raw)
In-Reply-To: <f7ccd24b0802231247i995186aif488282532fe5a6e@mail.gmail.com>
> Why should only the current buffer receive window change
> notifications? The fact that the hook is added locally should not
> affect that.
What would be the purpose of making a hook buffer-local if not running
it for the current buffer only?
>> What you see is the value reported after splitting the window not after
>> enlarging it.
>
> Which is an error, isn't it? Enlarging the window is a window
> configuration change.
Yes. But since you deliberately made the hook buffer-local it won't get
run :-(
I suppose what you want is to investigate all affected windows when the
corresponding configuration changes. This means we'd have to change
`delete-window', `enlarge-window', `shrink-window',
`adjust-window-trailing-edge' and `set-window-configuration' as to walk
all windows on the frame, check whether one of the associated buffers
has a non-nil local value for `window-configuration-change-hook', and
run that hook (in addition to a global hook). The question here is what
to do when the same buffer is shown in two or more windows on the
affected frame - should we call the hook twice in that case?
BTW, did you try how `window-size-change-functions' behaves in this
regard?
next prev parent reply other threads:[~2008-02-23 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 15:50 Wrong window end reported after splitting window Juanma Barranquero
2008-02-23 18:52 ` martin rudalics
2008-02-23 20:47 ` Juanma Barranquero
2008-02-23 22:36 ` martin rudalics [this message]
2008-02-24 2:08 ` Juanma Barranquero
2008-02-24 15:34 ` Stefan Monnier
2008-02-24 22:33 ` martin rudalics
2008-02-25 2:33 ` Stefan Monnier
2008-02-25 14:07 ` martin rudalics
2008-02-25 16:09 ` Stefan Monnier
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=47C09FFA.4040604@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.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 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.