unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 40273@debbugs.gnu.org
Subject: bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts
Date: Wed, 1 Apr 2020 22:33:18 +0200	[thread overview]
Message-ID: <20200401203318.GA6142@LionPure> (raw)
In-Reply-To: <20200331165559.6yfowbvtuoth6vdw@pelzflorian.localdomain>

Hi Florian,

On +2020-03-31 18:55:59 +0200, pelzflorian (Florian Pelz) wrote:
> On Tue, Mar 31, 2020 at 05:35:41PM +0200, Ludovic Courtès wrote:
> > I think we can have both Alt-Shift and what Mathieu implemented, no?
> > 
> 
> Yes, both would be best, what Mathieu implemented is more
> discoverable.
> 
> > However, note that the installed system won’t have Alt-Shift support,
> > and perhaps that is a bigger concern.
> 
> Yes.
> 
> guix build -S console-setup
> sudo mkdir -p /usr/share/X11
> cd /usr/share/X11
> sudo ln -s /gnu/store/fabcbhjh4g5fmm39fmkjjhiplqwrg0n8-console-setup-1.194-checkout/Keyboard/ckb xkb
> ckbcomp ar,fr -variant azerty, -option grp:alt_shift_toggle > ~/test
> sudo loadkeys ~/test
> 
> works, but I have no idea how to turn that into a keyboard-layout.
> I tried setting in /etc/config.scm
> 
>  (keyboard-layout
>   (keyboard-layout "ar,fr" "azerty" #:options '("grp:alt_shift_toggle")))
> 
> but it threw an error.
> 
> > OTOH, we’re just using the standard XKB layouts, so if they don’t
> > provide Alt-Shift, well, perhaps that’s because this is the way it’s got
> > to be?
> 
> I did not know back then, but it does work.  In dconf-editor, I can
> set org.gnome.desktop.input-sources to ['grp:alt_shift_toggle'].  It
> switches between all configured layouts in GNOME.
> 
> > Is “grp:alt_shift_toggle” guaranteed to be available, no what what
> > ‘layout’ is?
> > 
> > Also, that means Alt-Shift is enabled for all layouts, not just the
> > non-Latin layouts, right?
> 
> Yes, with the patch I can toggle any layout to US layout and back.
>

Have you looked at man vconsole.conf
    http://man7.org/linux/man-pages/man5/vconsole.conf.5.html

Could this be helpful?
    https://unix.stackexchange.com/q/57085

Also this has more extensive info on creating/modifying keymaps and
getting systemd to get them going:
    https://wiki.archlinux.org/index.php/Linux_console/Keyboard_configuration

I don't know if this is useful, but seems like you can affect things
early in the boot sequence (from the man page):
--8<---------------cut here---------------start------------->8---
       Note that the kernel command line options vconsole.keymap=,
       vconsole.keymap_toggle=, vconsole.font=, vconsole.font_map=,
       console.font_unimap= may be used to override the console settings at
       boot.
--8<---------------cut here---------------end--------------->8---

> I believe we would need a map from each layout to whether it should be
> QWERTY, AZERTY, QWERTZ …  Or we would just use QWERTY.
> 
> What do you think is the right path forward?

Do the right thing :)

> 
> Thank you.
> 
> Regards,
> Florian
> 

-- 
Regards,
Bengt Richter

  reply	other threads:[~2020-04-01 20:34 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)
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 [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20200401203318.GA6142@LionPure \
    --to=bokr@bokr.com \
    --cc=40273@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).