From: Olaf Hering <olh@suse.de>
To: Colin Leroy <colin@colino.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Fw: [PATCH] Right-click modifier
Date: Tue, 14 Oct 2003 11:36:04 +0200 [thread overview]
Message-ID: <20031014093604.GC29143@suse.de> (raw)
In-Reply-To: <02cc01c39231$dce0d200$3cc8a8c0@ANOSP>
On Tue, Oct 14, Colin Leroy wrote:
> [Forwarding, just in case.]
>
> > Hi,
> >
> > this patch adds an entry in /proc,
> > /proc/sys/dev/mac_hid/rclick_key_modifier.
> >
> > It lets the kernel report a right-click when KEY+Left click are pressed,
> > where KEY is the KEY specified by echoing its code to the /proc entry.
Its certainly a nice thing, but all this mouse button emulation stuff
should be handled in userland. Its just the question how and where.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-14 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 9:02 Fw: [PATCH] Right-click modifier Colin Leroy
2003-10-14 9:36 ` Olaf Hering [this message]
2003-10-14 10:27 ` Colin Leroy
2003-10-14 11:34 ` Franz Sirl
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=20031014093604.GC29143@suse.de \
--to=olh@suse.de \
--cc=colin@colino.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).