From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Mouse generating two mouse click events instead of one
Date: Fri, 28 Feb 2003 07:37:34 +0100 [thread overview]
Message-ID: <20030228063734.31846.qmail@linuxmail.org> (raw)
----- Original Message -----
From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
Date: 27 Feb 2003 23:46:37 +0000
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: Mouse generating two mouse click events instead of one
> On Thu, 2003-02-27 at 22:33, Felipe Alfaro Solana wrote:
> this often happends when you have two inputs in XFree86 config pointing
> to the same device.
But I don't... :-(
More ideas ;-)
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
next reply other threads:[~2003-02-28 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 6:37 Felipe Alfaro Solana [this message]
2003-02-28 10:36 ` Mouse generating two mouse click events instead of one binary man
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 11:40 Felipe Alfaro Solana
2003-02-27 22:33 Felipe Alfaro Solana
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=20030228063734.31846.qmail@linuxmail.org \
--to=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox