9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Jens K. Loewe" <jens.k.loewe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Trying to make 9front work on QWERTZ
Date: Thu, 25 Jul 2019 13:40:52 +0200	[thread overview]
Message-ID: <6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com> (raw)
In-Reply-To: <CA+cCjXrucUz9O0T=ku6nGG_-XYWGH5M3jy0xd=H9zFeVJ=6vGA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]

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 to 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ópez <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 change 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 kbdfs(8).
> 
> you should also ask this in the 9front ml.
> 
> 
> good luck.
> 
> -rodri
> 
>> On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com> wrote:
>> Can't give a definitive answer, but it works fine on my Norwegian keyboard which also has a rather different layout from the US keyboard. Unless the key code is simply not handled, I can't imagine why you get nothing at all.
>> 
>> 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?
>>> 

[-- Attachment #2: Type: text/html, Size: 2894 bytes --]

  reply	other threads:[~2019-07-25 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 19:01 Jens K. Loewe
2019-07-24 21:04 ` Ole-Hjalmar Kristensen
2019-07-25  7:17   ` Rodrigo G. López
2019-07-25 11:40     ` Jens K. Loewe [this message]
2019-07-26  5:59       ` Lucio De Re
2019-07-26 16:10         ` Jens K. Loewe
2019-07-26 19:54 Jonas Amoson
2019-07-27  9:21 cinap_lenrek
2019-07-27 19:18 ` Jens K. Loewe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com \
    --to=jens.k.loewe@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).