All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Suggestion] LILO-like direct menu item access && scripting
Date: Mon, 07 Feb 2005 17:33:37 +0000	[thread overview]
Message-ID: <87is54tgum.fsf@marco.marco-g.com> (raw)
In-Reply-To: <42077EA1.5090403@list.ru> (Serbinenko Vladimir's message of "Mon, 07 Feb 2005 15:43:45 +0100")

Serbinenko Vladimir <serbinenko.vova@list.ru> writes:

> Not at all because this syntax will mean that key is executed
> before choosing entry that I don't like. I propose the following
> syntaxes (I'm waiting for your suggestions which to use):

In that case you just should not press that key. :)

There is only the problem of key collisions (c is used for the
console, for example).  Perhaps 0-9, c-a and c-z can be used or so, I
personally don't care too much about this.

But it would be nice, IMHO, if it was clear which entry has which
hotkey.  Perhaps the title can be followed by the key in some
different color or so?

> entry "SuSE 7.3 (2.4.29)":l
> {
>     root (hd0,2)
>     kernel /boot/vmlinuz root=/dev/sda1 vga=extended rootflags=data=journal
> }

Personally I would prefer something like:

entry "SuSE 7.3 (2.4.29)" key="1"
{
    root (hd0,2)
    kernel /boot/vmlinuz root=/dev/sda1 vga=extended rootflags=data=journal
}

Or we could just give *every* menu item a hotkey and make it
configurable to make it visual (like I described above) or not.

Thanks,
Marco




  reply	other threads:[~2005-02-07 17:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 12:10 [Suggestion] LILO-like direct menu item access Marc-Jano Knopp
2005-02-07 14:43 ` [Suggestion] LILO-like direct menu item access && scripting Serbinenko Vladimir
2005-02-07 17:33   ` Marco Gerards [this message]
2005-02-07 23:24     ` Marc-Jano Knopp
2005-02-08 10:25       ` Serbinenko Vladimir
2005-02-08 20:56         ` Marc-Jano Knopp
2005-02-08 21:54           ` Marco Gerards
2005-02-08 21:48       ` Marco Gerards
2005-02-08 22:51         ` Marc-Jano Knopp
2005-02-09 10:21           ` Serbinenko Vladimir
2005-02-10 19:24             ` Yoshinori K. Okuji
2005-02-10 21:51               ` Marc-Jano Knopp
2005-02-11  9:38                 ` Yoshinori K. Okuji
2005-02-11 12:09                   ` Marc-Jano Knopp
2005-02-11 14:34                     ` Serbinenko Vladimir
2005-02-11 16:37                       ` Marc-Jano Knopp
2005-02-11 17:13                         ` Serbinenko Vladimir
2005-02-13 18:25                           ` Marc-Jano Knopp
2005-02-10 21:39             ` Marc-Jano Knopp
2005-02-08 13:20   ` Yoshinori K. Okuji
2005-02-08 16:21     ` Serbinenko Vladimir
2005-02-11 20:27       ` Marco Gerards
2005-02-11 22:01         ` Scripting Serbinenko Vladimir
2005-02-13 18:56           ` Scripting Marco Gerards
2005-02-13 19:39             ` Scripting Serbinenko Vladimir
2005-02-13 19:54             ` Scripting Hollis Blanchard
2005-02-14 21:39               ` Scripting Marco Gerards
2005-02-15 16:16                 ` Scripting Serbinenko Vladimir
2005-02-15 22:13                   ` Scripting Yoshinori K. Okuji
2005-02-07 17:20 ` [Suggestion] LILO-like direct menu item access Marco Gerards

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=87is54tgum.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --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.