From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: keyboard layout patches
Date: Mon, 18 Jan 2010 16:00:22 +0100 [thread overview]
Message-ID: <4B547786.7050509@gmail.com> (raw)
In-Reply-To: <20100118135335.GA28365@pinux.info>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Carles Pina i Estany wrote:
> Hi,
>
> I answer in fast way... more at evening. Items that I don't comment I
> understand and agree.
>
> On Jan/18/2010, Vladimir '??-coder/phcoder' Serbinenko wrote:
>
>
>>> How could grub-mkinstall (00_header.in) know the current keyboard in the
>>> system?
>>>
>> setxkbmap -print will give you the x layout but it won't work outside of X.
>>
>>> I wold tweak 00_header.in to generate the keymap file and setup
>>> it.
>>>
>>>
>> It may be executed by a daemon with no X available.
>>
>
> I'll use Felix suggestion: do whatever is in /etc/grub/default
>
>
>
>> + filename =
>> + grub_malloc (grub_strlen (prefix) + grub_strlen ("/") +
>> + grub_strlen (args[0]) + 1);
>> Can you add support for complete filenames?
>>
>
> do you mean that, for example, if args[0] starts by "/" then filename =
> args[0]?
>
> 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.
>> 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?
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
> Thanks for the other comments,
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-01-18 15:00 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 [this message]
2010-01-18 19:25 ` Carles Pina i Estany
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=4B547786.7050509@gmail.com \
--to=phcoder@gmail.com \
--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.