From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] if timeout is set to zero, don't bother drawing the menu
Date: Sun, 10 Feb 2008 21:07:27 +0100 [thread overview]
Message-ID: <200802102107.27787.okuji@enbug.org> (raw)
In-Reply-To: <20080210125533.GF1828@thorin>
On Sunday 10 February 2008 13:55, Robert Millan wrote:
> We could make the behaviour be, that if ESC is pressed at any time before
> an input line is completed, the operation is aborted, read returns
> non-zero, and it doesn't save the line to any variable. What do you think?
Not bad. :)
> > In GRUB Legacy, the hidden menu uses ESC, because if it uses ENTER, and
> > the user pushes ENTER too long, and a key repeat occurs, then the first
> > item may be selected quick as a flash. But we could avoid this problem by
> > vacuuming all inputs before showing a menu, so it might be acceptable to
> > use ENTER instead.
>
> This is still error-prone. Even if you vacuum the input buffer, we still
> have a race between user unholding ENTER and GRUB showing the menu.
> Vacuuming the buffer just gives us more time, but doesn't garantee good
> results.
Sure, but I think it would be good enough in reality.
> > (Actually, this should be implemented, regardless of this issue, because
> > some BIOSes may leave garbage in a key buffer. I don't remember if this
> > has been done for GRUB 2.)
>
> You mean garbage is present when control is transfered to GRUB, or
> generated afterwards? I assume the first, but then if any user input is
> attempted before removing the garbage, it may be corrupted. So it should
> be done as early as possible, shouldn't it? Perhaps in
> grub_console_init()?
Maybe. Personally, I don't mind even if it is done at the startup.
Okuji
next prev parent reply other threads:[~2008-02-10 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:18 [PATCH] if timeout is set to zero, don't bother drawing the menu Robert Millan
2008-02-09 10:59 ` Robert Millan
2008-02-09 20:03 ` Yoshinori K. Okuji
2008-02-09 22:09 ` Robert Millan
2008-02-10 7:10 ` Yoshinori K. Okuji
2008-02-10 12:55 ` Robert Millan
2008-02-10 20:07 ` Yoshinori K. Okuji [this message]
2008-02-10 20:24 ` Isaac Dupree
2008-02-28 10:57 ` Robert Millan
2008-02-28 22:25 ` Yoshinori K. Okuji
2008-03-03 22:22 ` Robert Millan
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=200802102107.27787.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.