Bug 484103 - wacomexpresskeys has no documentation (ie, no man page)
wacomexpresskeys has no documentation (ie, no man page)
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: wacomexpresskeys (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Aristeu Rozanski
: Desktop
Depends On:
  Show dependency treegraph
Reported: 2009-02-04 14:38 EST by Suzanne Hillman
Modified: 2012-06-20 09:30 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 487383 (view as bug list)
Last Closed: 2012-06-20 09:30:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Suzanne Hillman 2009-02-04 14:38:15 EST
Description of problem:
wacomexpresskeys has no documentation (ie, no man page). This would be really helpful to have, since the usage info is also a bit confusing (too technical).

Version-Release number of selected component (if applicable):

This is also likely true for RHEL5.
Comment 1 Suzanne Hillman 2009-02-04 15:02:42 EST
It is unclear what 'automatic device search' means for an empty command line, and there is no output to the screen when one does this.

The -h screen is rather wordy.

Not sure why -s says file/screen when it prints the output to the screen.

Not sure what -x does.

Not sure if -v is simply verbose output that happens to include events, or it's solely for events.
Comment 4 Jiri Pallich 2012-06-20 09:30:52 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.