From: Suhail Singh <suhailsingh247@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40456@debbugs.gnu.org
Subject: bug#40456: Invalid keyboard layouts pass through
Date: Fri, 06 Dec 2024 12:19:22 -0500 [thread overview]
Message-ID: <87wmgczq3p.fsf@gmail.com> (raw)
In-Reply-To: <87zhbphcnj.fsf@inria.fr> ("Ludovic Courtès"'s message of "Sun, 05 Apr 2020 22:59:28 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> Long story short: it would be great if invalid keyboard layouts were
> caught when the system is instantiated. It could be ‘ckbcomp’ errorring
> out, or we could have additional code that browses xkeyboard-config’s
> ‘base.xml’ file.
Ludo, this issue currently has the debbugs usertag "v1.3.0". Is that
usertag still applicable?
--
Suhail
prev parent reply other threads:[~2024-12-06 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 20:59 bug#40456: Invalid keyboard layouts pass through Ludovic Courtès
2021-03-04 17:01 ` Brice Waegeneire via web
2024-12-06 17:19 ` Suhail Singh [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
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=87wmgczq3p.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=40456@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).