unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierpaolo Bernardi <olopierpa@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22247@debbugs.gnu.org
Subject: bug#22247: 24.4; ghost mouse pointer
Date: Sun, 27 Dec 2015 18:44:37 +0100	[thread overview]
Message-ID: <CANY8u7Hcdi5FZ58jFtMww1acvdTAKwXSk=rhfEsY4iH9_zSLHQ@mail.gmail.com> (raw)
In-Reply-To: <83ziwvg5ek.fsf@gnu.org>

On Sun, Dec 27, 2015 at 6:36 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sun, 27 Dec 2015 18:22:52 +0100
>> From: Pierpaolo Bernardi <olopierpa@gmail.com>
>> Cc: rudalics@gmx.at, 22247@debbugs.gnu.org
>>
>> On Sun, Dec 27, 2015 at 6:11 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> > I don't even know what mouse tracks are.
>>
>> Microsoft calls them "trails", actually, sorry.
>>
>> When on, this feature makes the mouse pointer more apparent by making
>> it leave a trail behind it when moving.
>
> But then what you see is exactly what you asked for: the mouse trail,
> no?

No. Regular trails follow the pointer and fade away in less than a
second. When the mouse is still it shows normally, as if the feature
was off.

(Sorry for the delay, I will be able to do the test later today)





  reply	other threads:[~2015-12-27 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-26 15:34 bug#22247: 24.4; ghost mouse pointer Pierpaolo Bernardi
2015-12-26 18:59 ` Eli Zaretskii
2015-12-26 21:40   ` Pierpaolo Bernardi
2015-12-27 16:08     ` Eli Zaretskii
2015-12-27 16:58       ` Pierpaolo Bernardi
2015-12-27 17:11         ` Eli Zaretskii
2015-12-27 17:22           ` Pierpaolo Bernardi
2015-12-27 17:36             ` Eli Zaretskii
2015-12-27 17:44               ` Pierpaolo Bernardi [this message]
2015-12-27 18:18                 ` Eli Zaretskii
2015-12-27 18:54                   ` Eli Zaretskii
2015-12-28 22:15                     ` Pierpaolo Bernardi
2016-12-07 20:22                     ` Glenn Morris
2015-12-27 16:05 ` martin rudalics

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='CANY8u7Hcdi5FZ58jFtMww1acvdTAKwXSk=rhfEsY4iH9_zSLHQ@mail.gmail.com' \
    --to=olopierpa@gmail.com \
    --cc=22247@debbugs.gnu.org \
    --cc=eliz@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).