Documentation/input/input.txt.gz has a bug

Documentation/input/input.txt.gz has a bug

[jidanni]

/usr/share/doc/linux-doc-3.0.0/Documentation/input/input.txt.gz
Has an error at "(c, 13, 32)" or needs an explanation added:

  Doing a cat /dev/input/mouse0 (c, 13, 32) will verify that a mouse
is also emulated, characters should appear if you move it.

Bye.

Re: Documentation/input/input.txt.gz has a bug

[Ben Pfaff]

jidanni@jidanni.org writes:

> /usr/share/doc/linux-doc-3.0.0/Documentation/input/input.txt.gz
> Has an error at "(c, 13, 32)" or needs an explanation added:
>
>   Doing a cat /dev/input/mouse0 (c, 13, 32) will verify that a mouse
> is also emulated, characters should appear if you move it.

I think that it's correct:

    $ ls -l /dev/input/mouse0
    crw------- 1 root root 13, 32 Nov 12 09:14 /dev/input/mouse0
-- 
Ben Pfaff 
http://benpfaff.org

Re: Documentation/input/input.txt.gz has a bug

[jidanni]

>>>>> "BP" == Ben Pfaff <blp@cs.stanford.edu> writes:
BP>     $ ls -l /dev/input/mouse0
BP>     crw------- 1 root root 13, 32 Nov 12 09:14 /dev/input/mouse0
Yes, but say there what your are trying to say, or else all we know is
$ cat /dev/input/mouse0 (c, 13, 32)
bash: syntax error near unexpected token `('

Re: Documentation/input/input.txt.gz has a bug

[Bernd Petrovitsch]

Hi all!

On Die, 2011-11-15 at 14:21 +0800, jidanni@jidanni.org wrote:
> >>>>> "BP" == Ben Pfaff <blp@cs.stanford.edu> writes:
> BP>     $ ls -l /dev/input/mouse0
> BP>     crw------- 1 root root 13, 32 Nov 12 09:14 /dev/input/mouse0
> Yes, but say there what your are trying to say, or else all we know is
> $ cat /dev/input/mouse0 (c, 13, 32)
> bash: syntax error near unexpected token `('

You plain simply copied too much (and the parentheses also make
absolutely no sense for the "cat" command).
/dev/input/mouse0 is a _c_haracter device with major number _13_ and
minor number _32_.

	Bernd
-- 
Bernd Petrovitsch                  Email : bernd@petrovitsch.priv.at
                     LUGA : http://www.luga.at

Re: Documentation/input/input.txt.gz has a bug

[jidanni]

>>>>> "BP" == Bernd Petrovitsch <bernd@petrovitsch.priv.at> writes:
BP> You plain simply copied too much (and the parentheses also make
BP> absolutely no sense for the "cat" command).
BP> /dev/input/mouse0 is a _c_haracter device with major number _13_ and
BP> minor number _32_.
Yes, but the document needs to make that fact clear, as there will be
all levels of readers reading it. Else it will look like part of the
command to some.

Re: Documentation/input/input.txt.gz has a bug

[Randy Dunlap]

On 11/14/2011 05:24 PM, jidanni@jidanni.org wrote:
> /usr/share/doc/linux-doc-3.0.0/Documentation/input/input.txt.gz
> Has an error at "(c, 13, 32)" or needs an explanation added:
> 
>   Doing a cat /dev/input/mouse0 (c, 13, 32) will verify that a mouse
> is also emulated, characters should appear if you move it.


  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.

or

  Doing a
$ cat /dev/input/mouse
(which is char device 13,32) will verify that a mouse is also
emulated; characters should appear if you move it.


Do you want to submit a patch?

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: Documentation/input/input.txt.gz has a bug

[jidanni]

>>>>> "RD" == Randy Dunlap <rdunlap@xenotime.net> writes:
RD>   Doing a
RD> $ cat /dev/input/mouse
RD> (which is char device 13,32) will verify that a mouse is also
RD> emulated; characters should appear if you move it.
Looks great. Thanks!
RD> Do you want to submit a patch?
Please do it for me, as it's only a 1.5 per lifetime thing. Thanks.

Re: Documentation/input/input.txt.gz has a bug

[Bernd Petrovitsch]

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?

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  ----

	Bernd
-- 
Bernd Petrovitsch                  Email : bernd@petrovitsch.priv.at
                     LUGA : http://www.luga.at

Re: Documentation/input/input.txt.gz has a bug

[Randy Dunlap]

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 ***