Date: Fri, 22 Jan 1999 19:52:44 -0000 From: paul@originative.co.uk To: jfieber@indiana.edu, yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: current@FreeBSD.ORG Subject: RE: keymaps Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDD6@OCTOPUS>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: John Fieber [mailto:jfieber@indiana.edu] > Sent: Friday, January 22, 1999 3:51 PM > To: Kazutaka YOKOTA > Cc: current@FreeBSD.ORG > Subject: Re: keymaps > > > On Fri, 22 Jan 1999, Kazutaka YOKOTA wrote: > > > Gentlemen, I don't intend to add yet another keymap to > > /usr/share/syscons/keymaps. I am merely trying to define a > reasonable > > set of common, consistent key binding for existing keymaps. > > > > National keyboards have different layout of regular keys. But > > function keys and special keys are placed identically. They should > > work in the same way, or at least similar way in all > keyboards, unless > > there is a good reason to do otherwise. (I am not talking about > > non-AT keyboards which are totally different from either AT 84 or > > 101/102/104 keyboards.) > > What would be useful here is the ability to "compose" keymaps. > There would be basically two sets: one that defines the layout of > the main keyboard and one that defines the layout of the other > keys. That way I could pick my dvorak layout, then add on a > layout that, say, swaps control and caps lock but leaves the main > layout alone. I was thinking something similar, a way to dynamically modify the map ala xmodmap would be useful so that users who have particular preferences can implement the changes in, say, .login That's exactly what I do with xmodmap and X. The standard maps can continue to reflect the actual layout of the keyboards then rather than having a number of variations according to popular user preference. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A6D02246E1ABD2119F5200C0F0303D10FDD6>