Re: VM/MIME crashed XEmacs 21.0 "Poitou"

Kyle Jones writes: | Amir J. Katz writes: | > set-window-buffer(#<window on "INBOX" 0x8a31> #<buffer "INBOX">) | | 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. 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: --- window.c.orig-vmcrash Fri Oct 2 22:01:32 1998 +++ window.c Sat Oct 3 10:50:04 1998 ＠＠ -1635,7 +1635,8 ＠＠ /* this is not right, but much easier than doing what is right. */ /* w->start_at_line_beg = 0; */ /* WTF is this supposed to mean? GE */ - w->start_at_line_beg = beginning_of_line_p (XBUFFER (w->buffer), XINT (pos)); + w->start_at_line_beg = beginning_of_line_p (XBUFFER (w->buffer), + marker_position (w->start[CURRENT_DISP])); if (NILP (noforce)) w->force_start = 1; w->redo_modeline = 1; ＠＠ -3167,7 +3168,7 ＠＠ Fset_marker (w->sb_point, w->start[CURRENT_DISP], buffer); /* set start_at_line_beg correctly. GE */ w->start_at_line_beg = beginning_of_line_p (XBUFFER (buffer), - XBUFFER (buffer)->last_window_start); + marker_position (w->start[CURRENT_DISP])); w->force_start = 0; /* Lucid fix */ SET_LAST_MODIFIED (w, 1); SET_LAST_FACECHANGE (w); I think you have to apply this patch manually but it fixed the VM crash problem reported before which looked pretty much the same! --Marcus