From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Message-ID: From: "Adrian Regenfuss" To: 9fans@9fans.net Content-Type: text/html; charset=UTF-8 Date: Mon, 22 Dec 2014 15:30:24 +0100 Subject: [9fans] More kbmap information Topicbox-Message-UUID: 3768de36-ead9-11e9-9d60-3106f5b1d025

Hey everyone,

I am a bit intimidated to subscribe to a mailing list of an research OS...still being a student and not even able to write proper

English (I am german).

But I hope you can understand that.

Well, I have a little question about plan 9 as well...

After installing it on qemu, what was surprisingly easy, I wanted to use a non-qwert keyboard. But I found out that it wasn't

included. No problem, I thought, and began rewriting it. Here some links for tho layout (the last one is unfortunately german):

{

http://neo-layout.org/grafik/tastatur3d/tastatur_neo_Ebene1.png

http://neo-layout.org/grafik/tastatur3d/tastatur_neo_Ebene2.png

http://neo-layout.org/grafik/tastatur3d/tastatur_neo_Ebene3.png

http://neo-layout.org/grafik/tastatur3d/tastatur_neo_Ebene4png

http://neo-layout.org/grafik/tastatur3d/tastatur_neo_Ebene5.png

http://neo-layout.org/grafik/tastatur3d/tastatur_neo_Ebene6.png

http://www.neo-layout.org/

}

This layout is kind of tricky to implement, because it uses the caps lock key for the third level, but in my opinion it fits into plan 9, because it supports unicode pretty well. So, now, finally, my question: Where can I find more Information about

kbmap? I have searched for it quite a while and the man page does not provide very much.

Scharlatan

P.S:

IMHO:Setting the keyboard in linux is terrible...plan 9 makes it a lot better. Thanks for your help.

From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) From: Anthony Sorace In-Reply-To: Date: Mon, 22 Dec 2014 11:32:59 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <8477CDFC-C09A-4612-98C4-16020B5E27D4@9srv.net> References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] More kbmap information Topicbox-Message-UUID: 377102dc-ead9-11e9-9d60-3106f5b1d025 I don't think kbmap is going to give you what you want here. It's a = really easy way to set the non-modifier keys, but which modifier keys do = what is built into the underlying code. I don't think what you're after = would be too challenging, though; start by taking a look at = /sys/src/9/pc/kbd.c (assuming you're running a stock 32-bit kernel), in = particular the kbdputsc function. That said, after taking a look at the specific keyboard layout you've = described, I'd suggest living with the Plan 9 compose system for a while = first. Most folks have found it remarkably comfortable, at least if your = primary language doesn't vastly exceed what's on a keyboard (Japanese = &c). I know I miss it when I'm on every other system. Anthony From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 22 Dec 2014 08:44:39 -0800 To: 9fans@9fans.net Message-ID: In-Reply-To: <8477CDFC-C09A-4612-98C4-16020B5E27D4@9srv.net> References: <8477CDFC-C09A-4612-98C4-16020B5E27D4@9srv.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] More kbmap information Topicbox-Message-UUID: 3789e4b4-ead9-11e9-9d60-3106f5b1d025 On Mon Dec 22 08:29:52 PST 2014, a@9srv.net wrote: > I don't think kbmap is going to give you what you want here. It's a > really easy way to set the non-modifier keys, but which modifier keys > do what is built into the underlying code. I don't think what you're > after would be too challenging, though; start by taking a look at > /sys/src/9/pc/kbd.c (assuming you're running a stock 32-bit kernel), > in particular the kbdputsc function. > > That said, after taking a look at the specific keyboard layout you've > described, I'd suggest living with the Plan 9 compose system for a > while first. Most folks have found it remarkably comfortable, at > least if your primary language doesn't vastly exceed what's on a > keyboard (Japanese &c). I know I miss it when I'm on every other > system. one thing that is a bit unfortunate is that kbmap uses ibm pc scan codes. at this point it would be more sensible to use the usb key codes, and use the fact that there is a unique map of scan code to deal with ps/2 keyboards. this would allow more sensible specifications like leftshift instead of whatever scan code left shift is. it would also be more sensible for that to be the system keyboard interface, rather than the wierd 16-bit encoding that we've got. (it doesn't even properly deal with full-size mac keyboards.) i haven't done this for compaibility reasons, but it sure would be a good gsoc project. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Message-ID: From: "Adrian Regenfuss" To: 9fans@9fans.net Content-Type: text/html; charset=UTF-8 Date: Tue, 23 Dec 2014 15:47:24 +0100 In-Reply-To: References: <8477CDFC-C09A-4612-98C4-16020B5E27D4@9srv.net>, Subject: Re: [9fans] More kbmap information Topicbox-Message-UUID: 379b107c-ead9-11e9-9d60-3106f5b1d025

Okay, thank you very much!

I am going to take a look at kdb.

Have a nice Christmas!

Gesendet: Montag, 22. Dezember 2014 um 16:44 Uhr
Von: "erik quanstrom" <quanstro@quanstro.net>
An: 9fans@9fans.net
Betreff: Re: [9fans] More kbmap information

On Mon Dec 22 08:29:52 PST 2014, a@9srv.net wrote:
> I don't think kbmap is going to give you what you want here. It's a
> really easy way to set the non-modifier keys, but which modifier keys
> do what is built into the underlying code. I don't think what you're
> after would be too challenging, though; start by taking a look at
> /sys/src/9/pc/kbd.c (assuming you're running a stock 32-bit kernel),
> in particular the kbdputsc function.
>
> That said, after taking a look at the specific keyboard layout you've
> described, I'd suggest living with the Plan 9 compose system for a
> while first. Most folks have found it remarkably comfortable, at
> least if your primary language doesn't vastly exceed what's on a
> keyboard (Japanese &c). I know I miss it when I'm on every other
> system.

one thing that is a bit unfortunate is that kbmap uses ibm pc scan codes.
at this point it would be more sensible to use the usb key codes, and
use the fact that there is a unique map of scan code to deal with ps/2
keyboards. this would allow more sensible specifications like leftshift
instead of whatever scan code left shift is. it would also be more sensible
for that to be the system keyboard interface, rather than the wierd
16-bit encoding that we've got. (it doesn't even properly deal with
full-size mac keyboards.)

i haven't done this for compaibility reasons, but it sure would be a good
gsoc project.

- erik