From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [hober0@gmail.com: Re: mode-line redisplay bug]
Date: Fri, 12 Aug 2005 23:56:41 +0100 [thread overview]
Message-ID: <uu0huzrva.fsf@jasonrumney.net> (raw)
In-Reply-To: <E1E3b0D-0002kZ-To@fencepost.gnu.org> (Richard M. Stallman's message of "Fri, 12 Aug 2005 10:59:21 -0400")
"Richard M. Stallman" <rms@gnu.org> writes:
> His test case is very clear, but it does not fail when I try it.
> Can anyone else observe this failure?
I don't see this failure, but while trying to replicate it, I did see
some other display problems. I tried GNU/Linux and W32, I saw problems
on both when the mouse was over mouse-sensitive areas of the modeline,
but the symptoms were different.
If I hold the mouse above a mouse-sensitive part of the modeline while
switching buffers with C-c c as described in the original bug report,
I see the following:
On W32:
The highlighted portion of the modeline stays when the buffer
switches, overwriting any text that from the buffer that should appear
there. If I do the same in the header line of the *scratch* buffer,
the entire header line is erased as it should be.
On GNU/Linux:
The highlit area flickers. On W32 it flickers once when the tooltip
pops up, but on X, it flickers constantly. I remember fixing something
like this on W32 years ago, it was in the code that detected mouse
movement - movement events were being sent for zero movement when
inside track-mouse forms. But my recollection is that the same bug did
not appear on X at the time, so even though the code appeared to be
the same, I did not try to apply my fix to the X code.
If C-c c is pressed before the tooltip pops up, nothing happens until
the tooltip-delay expires, then the tooltip flashes up for a brief
instant and the buffer switch takes place.
Both problems I saw on GNU/Linux appear in both the header-line and
mode-line.
next prev parent reply other threads:[~2005-08-12 22:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 14:59 [hober0@gmail.com: Re: mode-line redisplay bug] Richard M. Stallman
2005-08-12 16:58 ` Eli Zaretskii
2005-08-12 17:19 ` Edward O'Connor
2005-08-12 17:31 ` Edward O'Connor
2005-08-12 18:58 ` Henrik Enberg
2005-08-16 12:58 ` Kim F. Storm
2005-08-12 18:19 ` Robert J. Chassell
2005-08-12 22:56 ` Jason Rumney [this message]
2005-08-13 21:54 ` Richard M. Stallman
2005-08-13 22:51 ` Jason Rumney
2005-10-08 21:26 ` Jason Rumney
2005-10-09 1:57 ` mituharu
2005-10-09 6:11 ` Jan D.
2005-10-10 19:40 ` Jason Rumney
[not found] ` <wlwtp6ijoz.wl%mituharu@math.s.chiba-u.ac.jp>
2005-10-11 1:21 ` YAMAMOTO Mitsuharu
2005-10-11 10:21 ` Kim F. Storm
2005-10-11 12:38 ` YAMAMOTO Mitsuharu
2005-10-11 15:14 ` Kim F. Storm
2005-10-11 14:50 ` Jason Rumney
2005-10-11 22:43 ` Kim F. Storm
2005-10-12 3:15 ` YAMAMOTO Mitsuharu
2005-10-12 8:39 ` Kim F. Storm
2005-10-12 8:41 ` YAMAMOTO Mitsuharu
2005-10-12 9:29 ` Kim F. Storm
2005-10-12 9:59 ` YAMAMOTO Mitsuharu
2005-10-11 10:47 ` Jason Rumney
2005-10-11 11:25 ` Kim F. Storm
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=uu0huzrva.fsf@jasonrumney.net \
--to=jasonr@gnu.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).