From: Randy Dunlap <rdunlap@xenotime.net>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
Cc: jidanni@jidanni.org, linux-kernel@vger.kernel.org
Subject: Re: Documentation/input/input.txt.gz has a bug
Date: Sun, 20 Nov 2011 12:19:15 -0800 [thread overview]
Message-ID: <4EC960C3.7040305@xenotime.net> (raw)
In-Reply-To: <1321447814.22548.18.camel@thorin>
On 11/16/2011 04:50 AM, Bernd Petrovitsch wrote:
> On Die, 2011-11-15 at 11:35 -0800, Randy Dunlap wrote:
> [...]
>> Doing a "cat /dev/input/mouse0" (char device 13,32) will verify that
>> a mouse is also emulated; characters should appear if you move it.
>> Doing a
>> $ cat /dev/input/mouse
>
> Hmm, how is this written in the other documentation?
There is very little consistency among all of the Documentation/ files
(hopefully there is some consistency within any one file).
I found many of:
a. using a prompt, e.g.:
$ cat /dev/input/mouse
b. using backquotes:
`cat /dev/input/mouse`
c. using double quotes:
"cat /dev/input/mouse"
d. using a colon:
type (or enter): cat /dev/input/mouse
> Both are fine with me. FWIW in emails and the like, I use backquotes
> usually as in
> ---- snip ----
> Doing a `cat /dev/input/mouse0` (char device 13,32) will verify that
> a mouse is also emulated; characters should appear if you move it.
> ---- snip ----
Yes, that's OK also.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-11-20 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 1:24 Documentation/input/input.txt.gz has a bug jidanni
2011-11-15 5:13 ` Ben Pfaff
2011-11-15 6:21 ` jidanni
2011-11-15 10:09 ` Bernd Petrovitsch
2011-11-15 11:12 ` jidanni
2011-11-15 19:35 ` Randy Dunlap
2011-11-15 20:04 ` jidanni
2011-11-16 12:50 ` Bernd Petrovitsch
2011-11-20 20:19 ` Randy Dunlap [this message]
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=4EC960C3.7040305@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bernd@petrovitsch.priv.at \
--cc=jidanni@jidanni.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 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.