all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 35585@debbugs.gnu.org
Subject: bug#35585: GRUB does not work with USB keyboards when using keyboard-layout
Date: Wed, 08 May 2019 12:03:21 +0200	[thread overview]
Message-ID: <87o94d1cwm.fsf@gnu.org> (raw)
In-Reply-To: <20190507183914.615660dc@scratchpost.org> (Danny Milosavljevic's message of "Tue, 7 May 2019 18:39:14 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Why is it specified at all?  If it's not specified, it will default to
> the "platform native" inputs which means the ones available in the source code
> for that platform.  So aren't we complicating our life for no reason by
> specifying it in the first place?

I don’t know.  I added it in 8d058e7b1b1a409d3d9cc29c5650a98db4e78783,
which was inspired by a patch posted by nee, but in hindsight I think
this has nothing to do here.  So I’m happy to remove that
“terminal_input” line.

Florian, can you check whether removing the line fixes the issue for
you?

We should make sure it also works for the rest of us.

Thanks for your feedback, Danny!

Ludo’.

  parent reply	other threads:[~2019-05-08 10:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 17:35 bug#35585: GRUB does not work with USB keyboards when using keyboard-layout pelzflorian (Florian Pelz)
2019-05-07 16:11 ` Ludovic Courtès
2019-05-07 16:39   ` Danny Milosavljevic
2019-05-07 22:09     ` pelzflorian (Florian Pelz)
2019-05-08 10:03     ` Ludovic Courtès [this message]
2019-05-08 12:23       ` pelzflorian (Florian Pelz)
2019-05-09 10:14         ` Ludovic Courtès
2019-05-09 12:52           ` Danny Milosavljevic
2019-05-13 13:59           ` Giovanni Biscuolo
2019-05-13 20:34             ` Ludovic Courtès
2019-05-07 17:25   ` pelzflorian (Florian Pelz)
2019-05-07 17:48     ` 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=87o94d1cwm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35585@debbugs.gnu.org \
    --cc=dannym@scratchpost.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 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.