Date: Tue, 9 Apr 1996 17:33:27 +0200 (MET DST) From: sos@FreeBSD.org To: kaleb@x.org (Kaleb S. KEITHLEY) Cc: sos@FreeBSD.org, hackers@freefall.FreeBSD.org Subject: Re: DVORAK keyboard drivers Message-ID: <199604091533.RAA01271@DeepCore.dk> In-Reply-To: <199604111454.KAA29763@exalt.x.org> from "Kaleb S. KEITHLEY" at Apr 11, 96 10:54:10 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Kaleb S. KEITHLEY who wrote:
>
> > kbdcontrol -l us.dvorak
> >
> > Its as easy as that...
> > X should inherit this from the console driver too...
> >
>
> If kbdcontrol gave us an easy way to tell what the keymap actually is,
> as opposed to a bunch of raw data. I don't want to have to try to parse
> a keymap to tell what it is.
I don't get the question here...
You load a keyboard map, so you should know what it is :)
If you see it from X and want to know the current map, just look
into the XFree sources, it does get it (I wrote the code years
ago, so I should know :) )
> And, as I said previously, nobody really uses the console, right? :-)
HA, I'll bet ALOT that there is a significant number of our users
that uses the console only !
> X has it's own way to load specific keymaps. I'm not opposed to having
> the X server DTRT based on what the console driver has loaded, e.g. see
> the X server sources for the Xdec and Xsun servers in R6.1, but we need
> better support from the OS to do it.
It's allready there, see above....
> (BTW, in 2.1.0R:
>
> %kbdcontrol -d > /tmp/keymap
> getting keymap: Inappropriate ioctl for device
>
> Any thoughts?)
Yeah, you didn't do this from a vty....
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604091533.RAA01271>