unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Latam keyboard layout changed, how can I get the old one back?
Date: Thu, 7 Apr 2022 11:50:50 +0200	[thread overview]
Message-ID: <20220407094012.jdk7jpzwpjtj5my4@pelzflorian.localdomain> (raw)
In-Reply-To: <W93m5R2O2plgVDwekJQHRCR6WRRfR5jTUaVcP3Iiymcd5KFgjQp1cqgO8_7xkEHSxKpdbiJDKPfWXv2hdRjb-WvVV-eUmII2LawL39ygbwo=@protonmail.com>

On Wed, Apr 06, 2022 at 10:00:55PM +0000, Luis Felipe wrote:
> I'm currently using Guix System (guix ab98b51), and noticed that I
> can't type less-than (<) and greater-than (>) signs anymore, even
> though I didn't change the keyboard-layout in my system definition
> (or anywhere else):

Perhaps a bug in xkeyboard-config, but there are no recent commits
changing xkeyboard-config.  If so, the virtual Linux console
(Ctrl+Alt+F2 etc.) should be affected too.  Is it?  Except you could
try a commit before and after bcfff754?  But I don’t see relevant
changes in

less /gnu/store/*-xkeyboard-config*/share/X11/xkb/symbols/latam

Xorg is using xf86-input-libinput now (guix commit 2e55a4c6b915), but
that cannot be at fault, because ab98b51ef is older …  I see no other
changes to Xorg in recent commits.

Regards,
Florian


  reply	other threads:[~2022-04-07  9:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 22:00 Latam keyboard layout changed, how can I get the old one back? Luis Felipe
2022-04-07  9:50 ` pelzflorian (Florian Pelz) [this message]
2022-04-07 15:22   ` Luis Felipe
2022-04-07 16:55     ` Luis Felipe
2022-04-08  9:47       ` pelzflorian (Florian Pelz)
2022-04-08 15:49         ` Luis Felipe
2022-04-10  0:40         ` Thiago Jung Bauermann
2022-04-10  9:50           ` pelzflorian (Florian Pelz)

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=20220407094012.jdk7jpzwpjtj5my4@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=luis.felipe.la@protonmail.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.
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).