all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Latam keyboard layout changed, how can I get the old one back?
Date: Fri, 08 Apr 2022 15:49:34 +0000	[thread overview]
Message-ID: <40LYLV4we2CXBcfv8nmoLIlU54pC_9BLJ-o4ZnKiTik-kiNcShsEaXYK8gkLHJ9ge4bolSwHFu42Ym8Js3K8m6t6122VYGBkM1AUBoiGSrY=@protonmail.com> (raw)
In-Reply-To: <20220408094726.gc3yzbodjvdy65j5@pelzflorian.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 540 bytes --]

On Friday, April 8th, 2022 at 9:47 AM, pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote:

> On Thu, Apr 07, 2022 at 04:55:11PM +0000, Luis Felipe wrote:
> 

> > I found a bug report upstream that may be related to this: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/267 .
> 

> 

> I guess there’s no way around `info "(guix) Using a Custom Guix Channel"` with (url "/home/luis/src/guix") and reverting bcfff754.

I think I'll keep entering UNICODE for now :)

Thanks again, Florian.

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

  reply	other threads:[~2022-04-08 15:50 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)
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 [this message]
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

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

  git send-email \
    --in-reply-to='40LYLV4we2CXBcfv8nmoLIlU54pC_9BLJ-o4ZnKiTik-kiNcShsEaXYK8gkLHJ9ge4bolSwHFu42Ym8Js3K8m6t6122VYGBkM1AUBoiGSrY=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=help-guix@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 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.