bug#24240: 25.1.50; window-state-put, image-mode and window scrolling

[Andreas Politz <politza@hochschule-trier.de>]

martin rudalics <rudalics@gmx.at> writes:

> It _should_ use NOFORCE anyway.

Ok.

> But do you mean that setting NOFORCE alone will handle your bug already
> and we don't need ‘frame-after-make-frame’ after all?

Yes, it would.

At least in the case of image-mode, it would actually be preferable to
let window-state-put override image-mode-reapply-winprops's scrolling,
because it has the correct value.  I don't know how familiar you are
with image-mode, but if it has no record for a particular window, it
restores the value last set in any window.  The difference would be
visible in case the buffer is shown in more than one window (with
different scroll values).

-ap