unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bug in incremental undrawing of mouseover highlighting
Date: Sun, 19 Nov 2006 18:45:24 -0500	[thread overview]
Message-ID: <17760.60564.194013.680591@rgrjr.dyndns.org> (raw)
In-Reply-To: <85u00v830n.fsf@lola.goethe.zz>

   From: David Kastrup <dak@gnu.org>
   Date: Sun, 19 Nov 2006 23:50:32 +0100

   Bob Rogers <rogers-emacs@rgrjr.dyndns.org> writes:

   >    It seems that mouseover background highlighting is not undrawn if
   > replaced by the same unhighlighted text.  This happens in the CVS
   > version as of late on 11-Nov.  (I have seen this bug for some time now,
   > but only just thought of a (relatively) easy way to reproduce it.)
   >
   >    To reproduce:
   >
   >    1.  "emacs -Q"
   >
   >    2.  "C-x d RET".  This gets a dired buffer; the exact directory
   > doesn't matter as long as it has at least a few files in it.  (And, for
   > some reason, "." and ".." don't count.)
   >
   >    3.  "C-x h M-w C-x b *scratch* RET C-y M-<".  This gets a copy of the
   > dired buffer contents; sometimes they come with dired fontification, and
   > sometimes not.  The same text should be displayed in the same character
   > positions in both dired and *scratch* buffers.
   >
   >    4.  "C-x b RET" to get back to the dired buffer, and move the mouse
   > over a file name so that it is highlighted in green.
   >
   >    5.  "C-x b RET" to return to *scratch*.  Notice that the same
   > characters in the same position are still highlighted in green.
   >
   >    6.  Move the mouse to a different file name.  Usually the
   > highlighting goes away, but sometimes it doesn't (and it doesn't
   > correlate with fontification).  If it does persist, type "C-x b RET" to
   > return once more to the dired buffer, and there will be two green file
   > names -- this can be repeated until every file name is green.

   For people wanting to debug this: I have the slight suspicion that the
   problem is masked usually because some well-meaning workaround
   suppresses the highlighting of partial lines that _should_ be
   highlighted when a buffer pops up under the mouse cursor.  Often the
   highlighting only starts once one moves the mouse cursor.  And I think
   that the problem might be triggered when only parts of the line are
   to be highlighted.

   I have no recipe for reproduction now, this is rather irregular and
   tends to occur in the newsreader for me, which means that there is no
   repeatable recipe.

   -- 
   David Kastrup, Kriemhildstr. 15, 44793 Bochum

Indeed; I first noticed this in vm-summary-mode, where each line
represents a message.  But there the whole line is highlighted.  When I
switch from the VM summary buffer to a buffer that matches the same line
in its entirety, all mouseover highlighting is preserved; when I switch
to a buffer that matches it partially, highlighting is correctly cleared
only for those positions that must be changed to display different
characters.

					-- Bob

  reply	other threads:[~2006-11-19 23:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 22:32 Bug in incremental undrawing of mouseover highlighting Bob Rogers
2006-11-19 22:50 ` David Kastrup
2006-11-19 23:45   ` Bob Rogers [this message]
2006-12-13 14:45     ` Stephen Berman
2006-12-13 16:04       ` Chong Yidong
2006-12-14  9:22         ` Stephen Berman
2006-12-16 12:31           ` Stephen Berman
2006-11-20  4:20   ` Eli Zaretskii
2006-11-20 19:22 ` Chong Yidong
2006-11-20 20:24   ` misleading install instruction in emacs/mac/INSTALL Gilbert Harman
2006-11-21  7:47     ` Richard Stallman
2006-11-22  8:23       ` YAMAMOTO Mitsuharu
2006-11-22 17:07         ` Gilbert Harman
2006-11-20 20:36   ` Bug in incremental undrawing of mouseover highlighting Eli Zaretskii
2006-11-22  4:06     ` Bob Rogers
2006-11-22 18:35       ` Eli Zaretskii
2006-11-22 15:07     ` Chong Yidong
2006-11-22 22:20       ` Eli Zaretskii
2006-11-22 23:57         ` Nick Roberts
2006-11-23  4:12           ` Eli Zaretskii
2006-11-23  4:50             ` Nick Roberts
2006-11-24 18:18               ` Eli Zaretskii
2006-11-25  1:53   ` YAMAMOTO Mitsuharu
2006-11-25  4:18     ` Chong Yidong
2006-11-25  7:28       ` YAMAMOTO Mitsuharu
2006-11-25 10:53         ` Eli Zaretskii
2006-11-25 16:18           ` Chong Yidong
2006-11-25 21:10             ` Eli Zaretskii
2006-11-26 19:05               ` Kim F. Storm
2006-12-26  2:26 ` Richard Stallman
2006-12-27  3:58   ` Bob Rogers
2006-12-27 21:16     ` Richard Stallman
2007-01-02 15:46       ` Kim F. Storm
2007-01-05  0:38         ` Michael Mauger
2007-01-19 15:33         ` Chong Yidong
2007-01-20 21:40           ` Stephen Berman
2007-01-21 14:36             ` Stephen Berman
2007-11-07 22:18               ` Stephen Berman
2007-01-23 16:28           ` John Paul Wallington

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=17760.60564.194013.680591@rgrjr.dyndns.org \
    --to=rogers-emacs@rgrjr.dyndns.org \
    --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).