From: martin rudalics <rudalics@gmx.at>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 24240@debbugs.gnu.org
Subject: bug#24240: 25.1.50; window-state-put, image-mode and window scrolling
Date: Wed, 17 Aug 2016 17:47:32 +0200 [thread overview]
Message-ID: <57B48714.40406@gmx.at> (raw)
In-Reply-To: <87mvkblm6o.fsf@hochschule-trier.de>
> (defmacro with-inhibit-window-configuration-change-hook (frame &rest body)
> "Inhibit `window-configuration-change-hook' on FRAME in BODY."
> (declare (indent 1) (debug t))
> (let ((frame-var (make-symbol "frame")))
> `(let ((,frame-var (window-normalize-frame ,frame)))
> (unwind-protect
> (progn
> (frame-after-make-frame ,frame-var nil)
> ,@body)
> (frame-after-make-frame ,frame-var t)))))
Good. We can use that (if we still need it).
>> Would my patch work around that?
>
> It seems to inhibit running the hook, but there is still the case of
> set-window-start in window--state-put-2. Using the NOFORCE works, but I
> don't know the implications of this in other cases.
It _should_ use NOFORCE anyway. Otherwise, when, for example, the size
of the window we got the state from is much larger than the size of the
window we put the state in, window-point will end up in the wrong place.
And ‘window-point’ is definitively more important than ‘window-start’.
It should be fairly easy to construct such an example.
But do you mean that setting NOFORCE alone will handle your bug already
and we don't need ‘frame-after-make-frame’ after all?
martin
next prev parent reply other threads:[~2016-08-17 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 23:05 bug#24240: 25.1.50; window-state-put, image-mode and window scrolling Andreas Politz
2016-08-16 11:00 ` martin rudalics
2016-08-16 13:51 ` Andreas Politz
2016-08-17 8:30 ` martin rudalics
2016-08-17 10:33 ` Andreas Politz
2016-08-17 15:47 ` martin rudalics [this message]
2016-08-17 16:12 ` Andreas Politz
2016-08-18 8:42 ` martin rudalics
2016-10-30 8:47 ` 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=57B48714.40406@gmx.at \
--to=rudalics@gmx.at \
--cc=24240@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
/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.