From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Treutwein Bernhard
<Bernhard.Treutwein@Verwaltung.Uni-Muenchen.DE>,
The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-mklayout - errors & unusable keyboard
Date: Mon, 27 Jun 2011 16:43:19 +0200 [thread overview]
Message-ID: <4E089707.4090909@gmail.com> (raw)
In-Reply-To: <239CEBDEE83EB949A48B6DB812AA19F603682C1F@ex2.zuv.uni-muenchen.de>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
On 27.06.2011 16:16, Treutwein Bernhard wrote:
> Hi Vladimir,
>
>> Filing a bug won't help me get more time to it. It would be much more
>> use if you supply the pairs of symbolic names and codepoints.
> The problem is (currently) that there a *lots* of unknown keys and
> I don't really know to which codepoints and or funtion keys these
> belong. See also attached list of error messages and the keymap
> which produced these errors. This keymap is fully compliant with
> the definition given in keymaps(5).
I'm fine with what grub-mklayout is able to do right now. I'm not
interested in reading through the tons of docs to know what the complete
definition is. If you're bothered by these problems, supply me with
either a patch or a definition which can be relatively easily
transformed into the code. Ideally a table which maps the symbols that
you have to what ckbcomp would have generated, possibly with wildcards.
> The guy who helped me to track down the problem has offered to
> write a complete parser, which will produce a table of the
> following form
>
> state keynumber actioncode
>
>
> where state reflects the shift/modifier state
> keynumber a hex code fo the key in question
> actioncode a codepoint for printable characters or
> symbol name for function keys
>
> this table should be easily parseable for grub-mklayout.
>
This would require almost complete rewrite of grub-mklayout. Again, not
interested in those.
We're in doocracy, best way to get anything done is to do it yourself
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next parent reply other threads:[~2011-06-27 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <239CEBDEE83EB949A48B6DB812AA19F603682C1F@ex2.zuv.uni-muenchen.de>
2011-06-27 14:43 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
[not found] <239CEBDEE83EB949A48B6DB812AA19F60368300B@ex2.zuv.uni-muenchen.de>
2011-06-28 8:30 ` grub-mklayout - errors & unusable keyboard Vladimir 'φ-coder/phcoder' Serbinenko
2011-06-28 9:04 ` Treutwein Bernhard
2011-06-28 9:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-06-13 16:36 grub-mklayout - different input format? Colin Watson
2011-06-15 13:11 ` grub-mklayout - errors & unusable keyboard Treutwein Bernhard
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=4E089707.4090909@gmail.com \
--to=phcoder@gmail.com \
--cc=Bernhard.Treutwein@Verwaltung.Uni-Muenchen.DE \
--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.