From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jens K. Loewe" Content-Type: multipart/alternative; boundary=Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Thu, 25 Jul 2019 13:40:52 +0200 Message-Id: <6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com> References: In-Reply-To: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 02ccdae6-eada-11e9-9d60-3106f5b1d025 --Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I tried using kbmap (which is not that easy without < and > on the keyboard)= , but the key still has no function for me. Weird, honestly. :-/ Thank you for the information that a 9front mailing list exists. I may want t= o look for that, although I guess that most of them are here as well. > Am 25.07.2019 um 09:17 schrieb Rodrigo G. L=C3=B3pez : >=20 > i have a qwertz but i use it with the us layout (any other layout sucks fo= r programming). i think you can change the layout with kbmap(1), and set it t= o de or whatever, although i don't have a 9 machine with me right now so can= 't tell for sure. >=20 > if the default map doesn't work, read it, ask on #cat-v@freenode and write= a new, fixed kbmap you can fling into kbdfs(8). >=20 > you should also ask this in the 9front ml. >=20 >=20 > good luck. >=20 > -rodri >=20 >> On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen wrote: >> Can't give a definitive answer, but it works fine on my Norwegian keyboar= d which also has a rather different layout from the US keyboard. Unless the k= ey code is simply not handled, I can't imagine why you get nothing at all. >>=20 >> ons. 24. jul. 2019, 21.03 skrev Jens K. Loewe : >>> Ahoy, >>>=20 >>> I've been trying to give 9front a test ride for a while now, and I'm >>> stuck with one specific problem. >>>=20 >>> So I have a German keyboard layout where <, > and | are on the same >>> key. However, while I have no problems with these keys, in 9front the >>> key seems to be dead on all of my keyboards. I tried quite a lot of >>> them, both inside QEMU on two different computers and on a dedicated >>> ThinkPad. Also, using the de layout does not fix that. >>>=20 >>> Is that a known problem or a configuration error? >>>=20 --Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I t= ried using kbmap (which is not that easy without < and > on the keyboa= rd), but the key still has no function for me. Weird, honestly. :-/

Thank you for the information that a= 9front mailing list exists. I may want to look for that, although I guess t= hat most of them are here as well.

Am 25.07.2019 u= m 09:17 schrieb Rodrigo G. L=C3=B3pez <rodrigosloop@gmail.com>:

i have a qwertz but i use it with= the us layout (any other layout sucks for programming). i think you can cha= nge the layout with kbmap(1), and set it to de or whatever, although i don't= have a 9 machine with me right now so can't tell for sure.

if the default map doesn't work, read it,= ask on #cat-v@freenode and write a new, fixed kbmap you can fling into kbdf= s(8).

you should also ask= this in the 9front ml.

good luck.

-rodri<= br>
On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com> wrote:

<= div class=3D"gmail_quote">
ons. 24. jul= . 2019, 21.03 skrev Jens K. Loewe <jens.k.loewe@gmail.com>:
=
Ahoy,

I've been trying to give 9front a test ride for a while now, and I'm
stuck with one specific problem.

So I have a German keyboard layout where <, > and | are on the same key. However, while I have no problems with these keys, in 9front the
key seems to be dead on all of my keyboards. I tried quite a lot of
them, both inside QEMU on two different computers and on a dedicated
ThinkPad. Also, using the de layout does not fix that.

Is that a known problem or a configuration error?

= --Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6--