From: Colin Watson <cjwatson@ubuntu.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] Clarify "Press any key to continue..." message
Date: Thu, 3 Apr 2014 18:11:06 +0100 [thread overview]
Message-ID: <20140403171106.GV32733@riva.ucam.org> (raw)
In-Reply-To: <533D92F2.1000602@redhat.com>
On Thu, Apr 03, 2014 at 12:57:22PM -0400, Prarit Bhargava wrote:
> On 04/03/2014 12:52 PM, Colin Watson wrote:
> > On Thu, Apr 03, 2014 at 12:49:50PM -0400, Prarit Bhargava wrote:
> >> I have mixed feelings about changing this message since it is such a
> >> well known message. OTOH, I've never really liked it myself.
> >
> > Surely nobody can really be depending on it; I don't see a problem with
> > changing that kind of text, in and of itself.
>
> Yeah ... but it is one of those things like the NMI dazed and confused message.
> Everyone knows about it, everyone agrees it could be better, but no one wants
> to change it because so much open documentation references it.
>
> Try googling linux + "Press any key to continue" and you'll see what I mean.
Of the first two pages of hits, only two relate to GRUB 2; and given
that there's still another instance of "Press any key to continue" in
the code, even those might not be relevant.
Anyway, I really don't think this is at all important given that most of
those hits are not exactly very informative anyway, and we should not
shy away from improving messages just because people have made terrible
attempts to explain what's going on with a previous version of the
message with an open-ended set of causes.
> > It's not necessarily "for menu" - you get this for errors after a menu
> > item has been selected too, and then it's just a delay before booting.
>
> Hmm ... really? After a menu item has been selected? I've never done that before.
Yes; for instance save_env in a menu item when /boot isn't writeable by
GRUB will do it.
> > Seems like a lot of effort. The actual delay is 2.5 seconds so a
> > countdown would look jumpy at the end ...
>
> Just do a countdown and change the delay to an even 3 seconds. Who is really
> going to care about a 1/2 second?
I don't think a countdown is necessary here, so I'm not going to spend
time writing code for it. But of course you're free to do so ...
--
Colin Watson [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2014-04-03 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:23 [PATCH] Clarify "Press any key to continue..." message Colin Watson
2014-04-03 16:49 ` Prarit Bhargava
2014-04-03 16:52 ` Colin Watson
2014-04-03 16:57 ` Prarit Bhargava
2014-04-03 17:11 ` Colin Watson [this message]
2014-04-03 17:15 ` Andrey Borzenkov
2014-04-07 17:25 ` Colin Watson
2014-07-23 7:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20140403171106.GV32733@riva.ucam.org \
--to=cjwatson@ubuntu.com \
--cc=grub-devel@gnu.org \
--cc=prarit@redhat.com \
/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.