From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: 35860@debbugs.gnu.org
Subject: bug#35860: Delayed window positioning after buffer display
Date: Wed, 19 Jun 2019 11:14:24 +0200 [thread overview]
Message-ID: <909a5c9c-74fa-a221-0ef1-6b9d61cb4cd0@gmx.at> (raw)
In-Reply-To: <87fto61ua5.fsf@mail.linkov.net>
> Adding such hooks would allow to get rid of macros easily.
> For example, instead of using two variables 'window-point-delayed'
> and 'window-start-delayed', a pre-display hook in 'view-lossage'
> will be able just to set a buffer-local run-once post-display hook
> that will adjust the window positions after the buffer is displayed
> in the window.
The problem is to properly clear these hooks to avoid that they affect
future, unrelated calls of 'display-buffer'. In most cases they are
supposed to be one-shots so a 'condition-case' in 'display-buffer'
should suffice, but it's a bit abnormal for hooks to get auto-cleared.
martin
next prev parent reply other threads:[~2019-06-19 9:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 20:32 bug#35860: Delayed window positioning after buffer display Juri Linkov
2019-05-23 4:34 ` Eli Zaretskii
2019-05-23 20:56 ` Juri Linkov
2019-05-24 6:32 ` Eli Zaretskii
2019-05-24 18:34 ` Juri Linkov
2019-05-25 7:58 ` martin rudalics
2019-05-27 19:49 ` Juri Linkov
2019-06-11 20:53 ` Juri Linkov
2019-06-13 8:44 ` martin rudalics
2019-06-13 20:24 ` Juri Linkov
2019-06-14 19:14 ` Juri Linkov
2019-06-15 8:17 ` martin rudalics
2019-06-15 22:44 ` Juri Linkov
2019-06-16 8:16 ` martin rudalics
2019-06-16 19:32 ` Juri Linkov
2019-06-17 8:23 ` martin rudalics
2019-06-17 20:33 ` Juri Linkov
2019-06-18 8:19 ` martin rudalics
2019-06-18 21:02 ` Juri Linkov
2019-06-19 9:14 ` martin rudalics [this message]
2019-06-19 21:34 ` Juri Linkov
2019-06-20 7:41 ` martin rudalics
2019-06-15 8:17 ` 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=909a5c9c-74fa-a221-0ef1-6b9d61cb4cd0@gmx.at \
--to=rudalics@gmx.at \
--cc=35860@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.