unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: david.ponce@wanadoo.fr, emacs-devel@gnu.org
Subject: Re: [hober0@bogus.example.com: Re: mode-line redisplay bug]
Date: Wed, 12 Oct 2005 15:42:31 +0200	[thread overview]
Message-ID: <m3k6giam2g.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <wlr7aqylem.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Wed, 12 Oct 2005 21:22:57 +0900")

YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:

>>>>>> On Wed, 12 Oct 2005 13:47:58 +0200 (CEST), David PONCE <david.ponce@wanadoo.fr> said:
>
>> Oops I spoke too fast.  Now I get the following message when the
>> mouse is over the read-only/modified status characters on the
>> mode-line:
>
>> Error during redisplay: (wrong-type-argument window-live-p nil) [126
>> times]
>
> Sorry.  I've been using the patch for a long time, but I didn't notice
> that.  The last change was backed out.

I think your change was pretty close to being ok.  Here is something
which seems to work for me on X -- maybe you can install it and adapt
it to W32 and MAC if it works for you too.

*** xterm.c	12 Oct 2005 14:42:03 +0200	1.883
--- xterm.c	12 Oct 2005 15:26:41 +0200	
***************
*** 3582,3588 ****
  static XMotionEvent last_mouse_motion_event;
  static Lisp_Object last_mouse_motion_frame;
  
! static void
  note_mouse_movement (frame, event)
       FRAME_PTR frame;
       XMotionEvent *event;
--- 3582,3588 ----
  static XMotionEvent last_mouse_motion_event;
  static Lisp_Object last_mouse_motion_frame;
  
! static int
  note_mouse_movement (frame, event)
       FRAME_PTR frame;
       XMotionEvent *event;
***************
*** 3596,3605 ****
        frame->mouse_moved = 1;
        last_mouse_scroll_bar = Qnil;
        note_mouse_highlight (frame, -1, -1);
      }
  
    /* Has the mouse moved off the glyph it was on at the last sighting?  */
!   else if (event->x < last_mouse_glyph.x
  	   || event->x >= last_mouse_glyph.x + last_mouse_glyph.width
  	   || event->y < last_mouse_glyph.y
  	   || event->y >= last_mouse_glyph.y + last_mouse_glyph.height)
--- 3596,3606 ----
        frame->mouse_moved = 1;
        last_mouse_scroll_bar = Qnil;
        note_mouse_highlight (frame, -1, -1);
+       return 1;
      }
  
    /* Has the mouse moved off the glyph it was on at the last sighting?  */
!   if (event->x < last_mouse_glyph.x
  	   || event->x >= last_mouse_glyph.x + last_mouse_glyph.width
  	   || event->y < last_mouse_glyph.y
  	   || event->y >= last_mouse_glyph.y + last_mouse_glyph.height)
***************
*** 3609,3615 ****
--- 3610,3619 ----
        note_mouse_highlight (frame, event->x, event->y);
        /* Remember which glyph we're now on.  */
        remember_mouse_glyph (frame, event->x, event->y, &last_mouse_glyph);
+       return 1;
      }
+ 
+   return 0;
  }
  
  \f
***************
*** 6483,6490 ****
      case MotionNotify:
        {
          previous_help_echo_string = help_echo_string;
!         help_echo_string = help_echo_object = help_echo_window = Qnil;
!         help_echo_pos = -1;
  
          if (dpyinfo->grabbed && last_mouse_frame
              && FRAME_LIVE_P (last_mouse_frame))
--- 6487,6493 ----
      case MotionNotify:
        {
          previous_help_echo_string = help_echo_string;
!         help_echo_string = Qnil;
  
          if (dpyinfo->grabbed && last_mouse_frame
              && FRAME_LIVE_P (last_mouse_frame))
***************
*** 6523,6529 ****
  
                  last_window=window;
                }
!             note_mouse_movement (f, &event.xmotion);
            }
          else
            {
--- 6526,6533 ----
  
                  last_window=window;
                }
!             if (!note_mouse_movement (f, &event.xmotion))
! 	      help_echo_string = previous_help_echo_string;
            }
          else
            {

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2005-10-12 13:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 11:47 [hober0@bogus.example.com: Re: mode-line redisplay bug] David PONCE
2005-10-12 12:22 ` YAMAMOTO Mitsuharu
2005-10-12 13:42   ` Kim F. Storm [this message]
2005-10-12 14:55     ` David Ponce
2005-10-13  8:22     ` YAMAMOTO Mitsuharu
  -- strict thread matches above, loose matches on Subject: below --
2005-10-12 11:37 David PONCE
2005-10-12 10:57 David PONCE
2005-10-12 11:20 ` YAMAMOTO Mitsuharu
2005-10-12 11:44   ` Kim F. Storm
2005-10-12 12:52     ` YAMAMOTO Mitsuharu
2005-10-12 13:40       ` Kim F. Storm
2005-10-13  8:21         ` YAMAMOTO Mitsuharu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3k6giam2g.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=david.ponce@wanadoo.fr \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).