(Sorry, I used the wrong reply button)
Sorry Eli, I don't know what you mean here. Over here the problem does
occur also in the GUI, and I am using the print to
'external-debugging-output' because the lwarn is what causes the
problem. I explained in the bug report that the window-start does not
get updated when including the lwarn after the forced redisplay (the
point is at 11, but window-start is still at 1).
(Also obviously, I can not use a normal print/message, when
'investigating' redisplay issues)
The documentation says that redisplay should recalculate the
window-start, and that by using force-window-update, we can ensure
that some buffer or window gets redisplayed on the next redisplay.
Now if you evaluate the code, from the bug report in GUI emacs, and
look at the last output printed to the terminal, it shows that the
window-start is still at 1, while it should be at 11, because I
applied the 'force-window-update' incl. the redisplay after the
(goto-char 11).
Is there something I am not understanding correctly? Or could I
consider it a bug in the documentation? As far as I know, I checked
the documentation and the behavior quite rigidly.