All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Harwood <rharwood@redhat.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org, javierm@redhat.com, phcoder@gmail.com,
	mchang@suse.com
Subject: Re: [PATCH v2 1/1] normal: Add paging instructions to interactive prompt
Date: Thu, 03 Nov 2022 17:50:51 -0400	[thread overview]
Message-ID: <jlgk04bwvus.fsf@redhat.com> (raw)
In-Reply-To: <20221103155812.qyuryvjmp5bfqrh3@tomti.i.net-space.pl>

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

Daniel Kiper <dkiper@net-space.pl> writes:

> On Mon, Oct 31, 2022 at 03:35:49PM -0400, Robbie Harwood wrote:
>> Conditionally add instructions for enabling paging to the prompt of
>> interactive shells.  This is not an ideal solution, as ineractive users
>> must always run a command in order to get the behavior they want, but it
>> avoids problematic interactions between prompting and sourcing files.
>>
>> Signed-off-by: Robbie Harwood <rharwood@redhat.com>
>> ---
>>  grub-core/normal/main.c | 4 +++-
>>  grub-core/normal/term.c | 6 ++++++
>>  include/grub/normal.h   | 1 +
>>  3 files changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/grub-core/normal/main.c b/grub-core/normal/main.c
>> index cb0e8e7fd2..d9d7c4ad28 100644
>> --- a/grub-core/normal/main.c
>> +++ b/grub-core/normal/main.c
>> @@ -411,9 +411,11 @@ grub_normal_read_line_real (char **line, int cont, int nested)
>>    if (cont)
>>      /* TRANSLATORS: it's command line prompt.  */
>>      prompt = _(">");
>> -  else
>> +  else if (grub_get_more())
>>      /* TRANSLATORS: it's command line prompt.  */
>>      prompt = _("grub>");
>> +  else
>> +    prompt = _("(enable paging with `set pager=1`) grub>");
>
> Do we really need to update prompt? Why do not print it once at the top
> of the screen after entering into normal mode first time?

My thinking was this: if a user enters the command prompt from the menu
and types "help", then not only is it not paginated, but the
instructions for enabling pagination have scrolled off the screen.
Rereading I do see that you and Vladimir were after the initial blob,
not the command line prompt.  I don't know if I agree that's
sufficient... will think about it more, I guess.

Be well,
--Robbie

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2022-11-03 21:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 19:35 [PATCH v2 0/1] Add paging instructions to interactive prompt Robbie Harwood
2022-10-31 19:35 ` [PATCH v2 1/1] normal: " Robbie Harwood
2022-11-03 15:58   ` Daniel Kiper
2022-11-03 21:50     ` Robbie Harwood [this message]
2022-11-04 12:59       ` Daniel Kiper

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=jlgk04bwvus.fsf@redhat.com \
    --to=rharwood@redhat.com \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=javierm@redhat.com \
    --cc=mchang@suse.com \
    --cc=phcoder@gmail.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.