All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: New commands (reboot, halt, help)
Date: Sat, 29 Jan 2005 15:11:07 +0000	[thread overview]
Message-ID: <87acqss22c.fsf@marco.marco-g.com> (raw)
In-Reply-To: <200501291530.37761.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sat, 29 Jan 2005 15:30:37 +0100")

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> On Saturday 29 January 2005 14:01, Marco Gerards wrote:
>> > Why do you test the flags with GRUB_COMMAND_FLAG_BOTH?
>>
>> Not all commands, for example `title', should be printed.
>
> Why?

I was under the impression title was a special case.  It does not even
have a description.

> And, do you know that GRUB_COMMAND_FLAG_BOTH is a sum of 
> GRUB_COMMAND_FLAG_CMDLINE and GRUB_COMMAND_FLAG_MENU? The conditional 
> is at least redundant.

Right.  What the code does is making sure GRUB_COMMAND_FLAG_CMDLINE
and GRUB_COMMAND_FLAG_MENU commands and commands with both set are
shown.  I fail to see the redundancy.

What do you propose?

>> This is a two column format.  The output is, for example:
> [snip]
>
> It's not a two-column format. Try help on bash. You will see what I 
> mean.

Right, I see.  I can make this change so it works more like GRUB
Legacy.

Is it ok if I add a --description so it works like the patch as it is
now?  It's how I like it, that's why I added it this way, but if you
don't like it I just remove it.

Thanks,
Marco






  reply	other threads:[~2005-01-29 15:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 12:36 New commands (reboot, halt, help) Marco Gerards
2005-01-28 12:52 ` chaac
2005-01-28 14:33   ` Marco Gerards
2005-01-28 18:54 ` Marco Gerards
2005-01-29  1:23 ` Yoshinori K. Okuji
2005-01-29 13:01   ` Marco Gerards
2005-01-29 14:30     ` Yoshinori K. Okuji
2005-01-29 15:11       ` Marco Gerards [this message]
2005-01-29 15:31         ` Serbinenko Vladimir
2005-01-29 16:17           ` Marco Gerards
2005-01-29 15:43         ` Marco Gerards
2005-01-29 17:47           ` Yoshinori K. Okuji
2005-01-29 17:45         ` Yoshinori K. Okuji
2005-01-29 18:36           ` Marco Gerards
2005-01-30 17:15 ` Marco Gerards

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=87acqss22c.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --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.