All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Clarify "Press any key to continue..." message
Date: Wed, 23 Jul 2014 09:44:01 +0200	[thread overview]
Message-ID: <53CF67C1.6080001@gmail.com> (raw)
In-Reply-To: <20140403142317.GT32733@riva.ucam.org>

[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]


Go ahead
On 03.04.2014 16:23, Colin Watson wrote:
> When grub_wait_after_message says "Press any key to continue...", it
> really means that it will continue anyway after a short delay, but that
> you can press a key to skip the delay.  Unfortunately, the delay is just
> long enough that in practice a number of users have time to see it,
> press a key, and then report a bug saying that their system won't boot
> without manual intervention, even though it would have booted just fine
> if they'd left it alone.  Rephrase this message to make it clearer
> what's really happening.
> 
> * grub-core/normal/menu.c (grub_wait_after_message): Rephrase
> message to make it clear that GRUB will continue even if the user
> does not press a key.
> ---
>  ChangeLog               | 6 ++++++
>  grub-core/normal/menu.c | 4 +++-
>  2 files changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/ChangeLog b/ChangeLog
> index 6eca73e..53c2aff 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,9 @@
> +2014-04-03  Colin Watson  <cjwatson@ubuntu.com>
> +
> +	* grub-core/normal/menu.c (grub_wait_after_message): Rephrase
> +	message to make it clear that GRUB will continue even if the user
> +	does not press a key.
> +
>  2014-03-31  Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
>  
>  	btrfs: fix get_root key comparison failures due to endianness
> diff --git a/grub-core/normal/menu.c b/grub-core/normal/menu.c
> index b47991a..a6fa93c 100644
> --- a/grub-core/normal/menu.c
> +++ b/grub-core/normal/menu.c
> @@ -63,7 +63,9 @@ grub_wait_after_message (void)
>  {
>    grub_uint64_t endtime;
>    grub_xputs ("\n");
> -  grub_printf_ (N_("Press any key to continue..."));
> +  grub_printf_ (N_(
> +    "Waiting a moment so that you can read previous messages.\n"
> +    "Press any key to skip this delay..."));
>    grub_refresh ();
>  
>    endtime = grub_get_time_ms () + 10000;
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

      parent reply	other threads:[~2014-07-24 21:37 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
2014-04-03 17:15     ` Andrey Borzenkov
2014-04-07 17:25       ` Colin Watson
2014-07-23  7:44 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=53CF67C1.6080001@gmail.com \
    --to=phcoder@gmail.com \
    --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.