On Wed, 28 Oct 1998, Marcus Thiessel wrote:
Kyle Jones writes:
| Amir J. Katz writes:
| > set-window-buffer(#<window on "INBOX" 0x8a31> #<buffer
| This seems to be a recurring theme. I'm also seeing at least one
| other weird recentering display behavior that makes me think
| something bad has happened to the redisplay. If anyone knows of
| recent redisplay code changes that might be responsible, please
| speak up.
Actually I think something good has happened to redisplay but then others
Gunnar Evermann already started speculation about that one since he
sent a redisplay and a Motif patch. He sent a fix which Georg Nikodym
and I tested:
Uh, it was rather a bit more than speculation! I produced a fix for the
problem of XEmacs crahsing in redisplay when displaying a window that had
just been widened. I rushed this fix a bit and it contained a dumb bug
(which now causes the crashes in VM) which is fixed by the patch Marcus
resent (it's also in CVS already).
Concerning the 'weird recentering' : What my patch does is to look at the
value of w->start_at_line_beg and if it is true, BUT 'start' is not really
at the beginnig of a line, it triggers a 'regenerate_window_point_center'.
Actually the code looked like this was the way someone had intended it to
work, but it didn't.
I had to modify some places (set_window_buffer and set_window_start or
something similar) to make sure that w->start_at_line_beg is actually set
to the correct value. There might still be other places that need
I think in VM you use set-window-start for scrolling or something like
that. If you set start to some value in the middle of a line this might
cause some recentering. if you can describe more precisely when this weird
stuff happens I can look into it when I get home (I only have XEmacs 19.13
here at the moment).
Sorry for the confusion.