From: Carles Pina i Estany <carles@pina.cat>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: keyboard layout patches
Date: Mon, 18 Jan 2010 19:25:37 +0000 [thread overview]
Message-ID: <20100118192537.GA14242@pina.cat> (raw)
In-Reply-To: <4B547786.7050509@gmail.com>
Hi,
On Jan/18/2010, Vladimir '??-coder/phcoder' Serbinenko wrote:
> Carles Pina i Estany wrote:
> > Actually if prefix (that it's a variable) is "/" then args[0] acts as a
> > filename. Would be like "///test/filename" and it's a valid directory.
> >
> >
> Perhaps we should remove prefix variables altogether.
I understand that you mean that the user would type:
load_keyboard /boot/grub/layouts/es
right? (in the shell or the config file)
Comments on this?
(I don't like it, I would even prefer to have the prefix hardcoded or
like it's now)
> >> Can you think of a way to restoring keyboard map to English?
> >>
> >
> > unloading the module restores the original keyboard (so, English one). I save
> > the original one when the module is loaded.
> >
> >
> I mean imagine that you're in a face to a grub with klingon keyboard
> how would you find your way out?
Klingon is my primary layout! :-)
I have different things to say and we could discuss quite long, but
let's jump to the ideas:
a) very short term: what about to register a command to "something"
(like "1234", numbers doesn't usually change between keyboard, right? or
"**" for the keypad -I should check that it works, but would fix if it
doesn't) that reverts to English?
b) medium term: as you suggested some days ago on IRC: Shift+Shift, or
Ctrl+Shift or something like this reverts to English.
I'm not sure about the infrastructure needed for b)
> Also keyboard_layouts is pretty small. Perhaps we can just make
> *_keyboard depend on it and put US keyboard into it as default and shave
> some complexity this way
How it would work in rescue mode and at_keyboard? I mean, extreme cases
that Grub for some reason could not reach the keyboard layout file.
The complexitity that we save is very reduced.
--
Carles Pina i Estany
http://pinux.info
next prev parent reply other threads:[~2010-01-18 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 0:10 keyboard layout patches Carles Pina i Estany
2010-01-18 8:15 ` Felix Zielcke
2010-01-18 13:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-18 13:53 ` Carles Pina i Estany
2010-01-18 15:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-18 19:25 ` Carles Pina i Estany [this message]
2010-01-18 19:31 ` Colin Watson
2010-01-18 22:17 ` Carles Pina i Estany
2010-01-19 23:21 ` Robert Millan
2010-01-20 0:03 ` Carles Pina i Estany
2010-01-19 23:19 ` Robert Millan
2010-01-18 20:04 ` Carles Pina i Estany
2010-01-19 23:22 ` Robert Millan
2010-01-18 23:27 ` Carles Pina i Estany
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=20100118192537.GA14242@pina.cat \
--to=carles@pina.cat \
--cc=grub-devel@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.
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.