From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: editing a menu entry
Date: Wed, 15 Sep 2004 11:35:18 +0200 [thread overview]
Message-ID: <200409151135.18142.okuji@enbug.org> (raw)
In-Reply-To: <87pt4oq1cw.fsf@marco.marco-g.com>
On Tuesday 14 September 2004 18:09, Marco Gerards wrote:
> That is nice! Have you thought about using tab completion here?
Not yet completely. Probably we will want to have a common completion
routine shared by menu editing and command-line handling. In the menu
interface, I think we can use some different ways to show candidates
potentially:
1. Show a list of available things (devices/files/commands) at the
bottom of the screen (out of the menu box).
2. Split the menu box temporarily and show a list.
3. Overwrite a list on the menu box with the colors flipped (white
background and black foreground) temporarily.
I think 1 and 3 are zsh-like, and 1 and 2 are Emacs-like. 1 is the
easiest to implement, but it can show very few candidates at a time.
> AFAIK emacs has combinations of keys because there are not enough
> keys for every function. I don't think GRUB will ever have this
> problem so an unusual key would be the best IMHO. It is easier for
> users and easier to implement.
Actually, we need a key to enter the command-line interface as well as
one to boot. So maybe C-c for a command-line and C-x for booting. I
don't want to use C-z, C-w or C-q, because the positions are different
between QWERTY and AZERTY.
Okuji
next prev parent reply other threads:[~2004-09-15 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 14:12 editing a menu entry Yoshinori K. Okuji
2004-09-14 14:27 ` Tobias Wollgam
2004-09-14 15:23 ` Yoshinori K. Okuji
2004-09-14 16:09 ` Marco Gerards
2004-09-15 9:35 ` Yoshinori K. Okuji [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 8:22 lode leroy
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=200409151135.18142.okuji@enbug.org \
--to=okuji@enbug.org \
--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.