>>>SET_PT_BOTH (opoint, opoint_byte); > > >>still spoils everything on Windows. Commenting out that line works, >>though. > > > Hmm, I couldn't test on Windows, and my previous patch worked on Mac > OS X (both X11 and Carbon) and Solaris for the original problem.
Hence the original problem is present on these platforms? Anyway, I'll have to wait what Windows XP people say about this. >>I continue to have no idea how current_column gets called with >>Qinhibit_point_motion_hooks not bound to Qt here ... > > > Maybe you can find such traces by setting a breakpoint to > current_column with the condition `Vinhibit_point_motion_hooks == > Qnil'. I found the following cases: > > pos_visible_p -> display_mode_line > echo_area_display -> redisplay_mode_lines -> display_mode_lines -> display_mode_line Thanks, I'm aware of these. I don't understand why pos_visible_p should be called by redisplay. For the second one I earlier tried to specbind Qinhibit_point_motion_hooks around it - to no avail. I have to retry. In any case this would just solve the current_column problem. There are, however, no restrictions as to what the modeline is allowed to display. Hence, this problem may raise it's ugly head whenever modeline calculations set point. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
