all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jonathan McHugh" <indieterminacy@libre.brussels>
To: "Josua Stingelin" <josuast@hotmail.com>, help-guix@gnu.org
Subject: Re: Getting the neo keyboard layout to work as expected
Date: Sun, 08 Aug 2021 16:57:26 +0000	[thread overview]
Message-ID: <36c1bf1c9bcc77729a3c751bdc192d82@libre.brussels> (raw)
In-Reply-To: <DB9PR06MB7657D819DF42E898AA2AD16BAAF59@DB9PR06MB7657.eurprd06.prod.outlook.com>

Josua,

Though Im not (yet) in a position to help, thanks for flagging Neo. Despite being merely an anglophone, I recognise some of the nice design decisions.

These seem more appropriate for my usecases
=> https://github.com/jackrosenthal/threelayout
=> http://www.adnw.de/index.php?n=Main.OptimierungF%c3%bcrDieGeradeTastaturMitDaumen-Shift

Ta

====================
Jonathan McHugh
indieterminacy@libre.brussels

August 8, 2021 12:54 PM, "Josua Stingelin" <josuast@hotmail.com> wrote:

> Hi!
> 
> So I'm having a puzzling experience using the neo keyboard layout.
> 
> Configuring the keyboard-layout in the system configuration using
> 
> (keyboard-layout (keyboard-layout "de" "neo" #:model "pc105"))
> 
> does not have the same effect as loading it using
> 
> loadkeys neo.
> 
> For some reason the Layer 4 key results in the same characters as the Layer 3
> instead of providing a numberblock and navigation (see
> https://www.neo-layout.org for the expected output).
> 
> There may be further differences but I suppose you get the point. Any idea what
> I'm doing wrong?
> 
> Thank you kindly for your assistance,
> Josua


      reply	other threads:[~2021-08-08 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08  8:21 Getting the neo keyboard layout to work as expected Josua Stingelin
2021-08-08 16:57 ` Jonathan McHugh [this message]

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=36c1bf1c9bcc77729a3c751bdc192d82@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=help-guix@gnu.org \
    --cc=josuast@hotmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.