All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Vogel <Andreas.Vogel@anvo-it.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Enhanced hotkey handling for menuentry
Date: Sat, 03 Mar 2012 22:30:43 +0100	[thread overview]
Message-ID: <4F528D83.4020603@anvo-it.de> (raw)
In-Reply-To: <4F5286AD.1000506@gmail.com>


> On 03.03.2012 21:43, Andreas Vogel wrote:
>> Here is a small patch which enhances the hotkey handling for menu
>> entries.
> Could you use GNU style? You miss the spaces before braces.
Sure. Missed by accident.

> Comments have to be full sentences, start with uppercase and end with
> a dot followed by 2 spaces.
Wow... ok.

> Comment /*NOTHING*/ is not useful.
I disagree, because it's more clear that this is an intentionally left
empty body. But it's a matter of taste and I obey.

>>          - new static function parse_key()
>>          - hotkey aliases are now case insensitive
>>          - additional hotkey aliases
> All added aliases conflict with normal function of these keys (arrows
> and pages)
Yes, I know. But it doesn't harm anyway and it might be useful to have
the code already in case the use of the keys change in the future.
Anyway, if you insist of leaving them out i'll obey.

>>          - handling now<SHIFT>  and<CTRL>  modifiers for hotkeys
> Could you change to the emacs notation?
What is the emacs notation? I have no idea.

> Shift flag isn't valid with alphanumeric keys.
Ah, ok. Am I right that it's enough just not to set the SHIFT mask in
case isalnum() is true?



  reply	other threads:[~2012-03-03 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 20:43 [PATCH] Enhanced hotkey handling for menuentry Andreas Vogel
2012-03-03 21:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-03 21:30   ` Andreas Vogel [this message]
2012-03-04 12:23     ` Andreas Vogel

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=4F528D83.4020603@anvo-it.de \
    --to=andreas.vogel@anvo-it.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.