[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: xkb rules for Thinkpad extra keys



On Thu, Jul 15, 2004 at 12:38:43PM +0300, Hile Tuohela wrote:
> I have written a small set of xkb rules to enable the extra keys
> on thinkpad laptops (keysyms 233 and 234). The rules implement 
> new keyboard model 'thinkpad'.
> 
> The files are available with a html README from 
> http://hile.dyndns.org/xkb-thinkpad.tgz
> 
> You can probably just run diff for the files under xkb directory,
> the changes are quite trivial. It would be great if these configs
> would end up being part of the packages and upstream. 
> 
> There might be problems with the rules and the fact these rules 
> replace the pc101,pc102 and other 'model' parameters in XF86Config-4,
> works for me at least with finnish keyboard.
> 
> I think my mapping of 'Prev/Next_Virtual_Screen' is good to not mix
> the keys with any other, possibly used keys, and most likely map 
> nicely to the tasks most people would do with these keys now: I see
> no other use for these keys except virtual desktop switching and 
> window moving.

Please file a wishlist-severity bug against the "xlibs" package with this
request so that we do not lose track of it.

One of the best ways to do this is with the "reportbug" package and command
of the same name.  One way to install reportbug is with "apt-get"; for
example:

  # apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.

  $ reportbug --mode=novice
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.

  $ reportbug
  Please enter the name of the package in which you have found a problem,
  or type 'other' to report a more general problem.
  >

The reportbug command is extensively documented in its usage message and
manual page.  Commands to view these pieces of documentation are:

  $ reportbug --help | more
  $ man reportbug

(The output of the above commands has been omitted from this message.)

Thanks for offering your contribution.  We look forward to reviewing it.

-- 
G. Branden Robinson                |      It doesn't matter what you are
Debian GNU/Linux                   |      doing, emacs is always overkill.
branden@debian.org                 |      -- Stephen J. Carpenter
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature


Reply to: