all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 40273@debbugs.gnu.org
Subject: bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts
Date: Mon, 30 Mar 2020 12:44:49 +0200	[thread overview]
Message-ID: <20200330104449.ahyivwdn62g6jluw@pelzflorian.localdomain> (raw)
In-Reply-To: <87a740nu0u.fsf@gmail.com>

On Sat, Mar 28, 2020 at 08:45:05PM +0100, Mathieu Othacehe wrote:
> Maybe we could add a help menu with <F1> key shortcut. From that
> help menu, one could change the current keyboard layout from any
> installation step?
> 

Yes, that is definitely a good place, *but* now that I saw Debian, it
would be good to additionally have a key combination.  I think
switching in an F1 help menu is more discoverable and having both
would be good.

From what an Arab friend told me, they are used to a key combination
(Alt+Shift if I remember correctly, as is Debian’s default; Debian
makes the combination configurable).  But I cannot figure out how to
make loadkeys use a key combination; ckbcomp seems not to produce
right results.

In QEMU on the compatibility console I ran “sendkey ctrl-alt-f3“.  I
then tried:

guix environment --ad-hoc console-setup #so I can run ckbcomp
mkdir -p /usr/share/X11/
cd /usr/share/X11
ln -s $(guix build -S console-setup)/Keyboard/ckb xkb
ckbcomp ar, -variant azerty, -option grp:toggle > ~/test
loadkeys us #so I can switch back, I hoped, but it does not work
loadkeys ~/test

But now I can only type Arabic.  Maybe it is because of QEMU.

I tried changing the keyboard-layout in /etc/config.scm, but then I
can no longer type my password.

Regards,
Florian

  reply	other threads:[~2020-03-30 10:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 13:42 bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts pelzflorian (Florian Pelz)
2020-03-28 19:45 ` Mathieu Othacehe
2020-03-30 10:44   ` pelzflorian (Florian Pelz) [this message]
2020-03-30 11:35     ` Mathieu Othacehe
2020-03-30 17:11       ` pelzflorian (Florian Pelz)
2020-03-30 17:31         ` pelzflorian (Florian Pelz)
2020-03-31 15:35         ` Ludovic Courtès
2020-03-31 16:55           ` pelzflorian (Florian Pelz)
2020-04-01 20:33             ` Bengt Richter
2020-04-02  6:24               ` pelzflorian (Florian Pelz)
2020-04-02  9:45             ` Ludovic Courtès
2020-04-03  0:38               ` pelzflorian (Florian Pelz)
2020-04-03  1:11                 ` pelzflorian (Florian Pelz)
2020-04-03 13:31                 ` pelzflorian (Florian Pelz)
2020-04-03 13:59                 ` pelzflorian (Florian Pelz)
2020-04-03 15:20                 ` Ludovic Courtès
2020-04-03 15:56                   ` pelzflorian (Florian Pelz)
2020-04-05 14:03                     ` Ludovic Courtès
2020-04-05 20:02                       ` pelzflorian (Florian Pelz)
2020-04-05 21:26                         ` Ludovic Courtès
2020-03-29 15:04 ` Ludovic Courtès
2020-03-29 17:16   ` pelzflorian (Florian Pelz)
2020-03-29 17:53     ` Mathieu Othacehe
2020-03-30 10:39       ` Mathieu Othacehe
2020-03-30 12:39         ` pelzflorian (Florian Pelz)
2020-03-31 15:29         ` Ludovic Courtès
2020-04-01 12:49           ` Mathieu Othacehe
2020-03-31 15:28       ` Ludovic Courtès
2020-04-01 12:52         ` Mathieu Othacehe
2020-04-02 10:25           ` Ludovic Courtès
2020-04-02 11:40             ` Mathieu Othacehe
2020-04-06  7:52               ` Ludovic Courtès
2020-04-06 13:14                 ` Mathieu Othacehe
2020-04-07  9:49                   ` Ludovic Courtès
2020-04-07 17:14                     ` Mathieu Othacehe
2020-04-02 23:27             ` Bengt Richter
2020-04-03 23:17               ` pelzflorian (Florian Pelz)
2020-04-08  7:20                 ` Bengt Richter
2020-04-08  9:42                   ` Ludovic Courtès
2020-04-08 21:11                     ` Bengt Richter

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=20200330104449.ahyivwdn62g6jluw@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=40273@debbugs.gnu.org \
    --cc=m.othacehe@gmail.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.