From: Jason Rumney <jasonr@f2s.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 806@emacsbugs.donarmstrong.com
Subject: bug#806: overlay display artifact: trace left behind
Date: Tue, 09 Dec 2008 23:36:05 +0800 [thread overview]
Message-ID: <493E9065.6090504@f2s.com> (raw)
In-Reply-To: <jiy72idwl4.fsf@fencepost.gnu.org>
Hi Drew,
Do you still see the bug below? I tried to follow your recipe, but the
behaviour I saw was sufficiently different from that described that I am
not sure that my tests are conclusive.
> Package: emacs,w32
>
> (Filing a report for old item from FOR-RELEASE.)
>
> http://lists.gnu.org/archive/html/emacs-devel/2006-08/msg00439.html
>
> Initial report (todo: verify new font backend eliminates this and other
> Cleartype related problems):
>
> 1. emacs -Q
>
> 2. Load this file: http://www.emacswiki.org/cgi-bin/wiki/mouse%2b.el
>
> 3. Customize this face to have a red foreground:
> `mouse-flash-position'. (The default, yellow, is not very visible
> against an emacs -Q background.)
>
> 4. M-: (global-set-key [down-mouse-2] 'mouse-flash-position)
>
> 5. Select some text (e.g. a word), for yanking elsewhere.
>
> 6. Put the mouse on some line of text. Press `mouse-2' and hold it
> pressed. Move the mouse along the text without releasing the button.
> Release it to finish the yank.
>
> When you press `mouse-2', the yank position is highlighted. When you
> move the mouse, the highlight moves with the mouse. But vestigial
> overlay traces are left behind.
>
>
>
>
>
next parent reply other threads:[~2008-12-09 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1228875410.493f26925c795@webmail.freedom2surf.net>
[not found] ` <jiy72idwl4.fsf@fencepost.gnu.org>
2008-12-09 15:36 ` Jason Rumney [this message]
2008-12-10 1:59 ` bug#806: overlay display artifact: trace left behind Drew Adams
2008-12-10 2:25 ` bug#806: marked as done (overlay display artifact: trace left behind) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493E9065.6090504@f2s.com \
--to=jasonr@f2s.com \
--cc=806@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.