changeset 34440:6fff04f818fa

(try_cursor_movement): Check update_mode_lines instead of the window's update_mode_line flag, since the former is set by force-mode-line-update, not the latter. This makes column-number-mode slightly faster.
author Gerd Moellmann <gerd@gnu.org>
date Mon, 11 Dec 2000 14:50:07 +0000
parents cb07a94d7b5a
children 3fdc6106c2a1
files src/xdisp.c
diffstat 1 files changed, 6 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/src/xdisp.c	Mon Dec 11 14:37:14 2000 +0000
+++ b/src/xdisp.c	Mon Dec 11 14:50:07 2000 +0000
@@ -9144,16 +9144,14 @@
      not moved off the frame.  */
   if (/* Point may be in this window.  */
       PT >= CHARPOS (startp)
-      /* If we don't check this, we are called to move the cursor in a
-	 horizontally split window with a current matrix that doesn't
-	 fit the display.  */
-      && !windows_or_buffers_changed
       /* Selective display hasn't changed.  */
       && !current_buffer->clip_changed
-      /* If force-mode-line-update was called, really redisplay;
-	 that's how redisplay is forced after e.g. changing
-	 buffer-invisibility-spec.  */
-      && NILP (w->update_mode_line)
+      /* Function force-mode-line-update is used to force a thorough
+	 redisplay.  It sets either windows_or_buffers_changed or
+	 update_mode_lines.  So don't take a shortcut here for these
+	 cases.  */
+      && !update_mode_lines
+      && !windows_or_buffers_changed
       /* Can't use this case if highlighting a region.  When a 
          region exists, cursor movement has to do more than just
          set the cursor.  */