From: Hubert Kario <kario@wit.edu.pl>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] add detailed help messages to btrfs command
Date: Tue, 12 Jul 2011 12:40:06 +0200 [thread overview]
Message-ID: <201107121240.06740.kario@wit.edu.pl> (raw)
In-Reply-To: <4E1B1309.2080408@jan-o-sch.net>
On Monday 11 of July 2011 17:13:13 Jan Schmidt wrote:
> Hi Hubert,
>
> I have to admit I did not recognize this patch but now Hugo is forcing
> me to use the "detailed help messages" and I've got an improvement to
> suggest:
>
> On 23.01.2011 13:42, Hubert Kario wrote:
[snip]
> > { do_defrag, -1,
> >
> > "filesystem defragment", "[-vcf] [-s start] [-l len] [-t size]
> > <file>|<dir> [<file>|<dir>...]\n"
> >
> > - "Defragment a file or a directory."
> > + "Defragment a file or a directory.",
> > + "[-vcf] [-s start] [-l len] [-t size] <file>|<dir>
> > [<file>|<dir>...]\n" + "Defragment file data or directory
> > metadata.\n"
> > + "-v be verbose\n"
> > + "-c compress the file while defragmenting\n"
> > + "-f flush data to disk immediately after
> > defragmenting\n" + "-s start defragment only from byte
> > onward\n" + "-l len defragment only up to len
> > bytes\n"
> > + "-t size minimal size of file to be considered for
> > defragmenting\n"
>
> Lots of too long lines.
you mean the code or the printed messages?
messages fit a 80 column screen, I remember I double checked it
>
> I don't like to repeat the synopsis passage. How about adding the
> general ->help when printing ->adv_help as well? This reduces the need
> of duplication.
I think I added it because of differences in formatting.
Also I'd say we don't want to overload the user with information when he
mistypes a command so the main help command should be as concise as possible
while the advanced may be much more detailed (looking at the mailing list, `fi
df` could definitely use some more verbose help message)
>
> To prove my point, looking at the current version in Hugo's integration
> branch, your two synopsis lines already got inconsistent regarding the
> -c option :-)
That's because the patches are submitted with base as Chris tree, not the
Hugo's so the result is a real patchwork that needs some clean-up
[snip]
> > @@ -148,10 +184,10 @@ static void help(char *np)
> >
> > printf("Usage:\n");
> > for( cp = commands; cp->verb; cp++ )
> >
> > - print_help(np, cp);
> > + print_help(np, cp, BASIC_HELP);
> >
> > printf("\n\t%s help|--help|-h\n\t\tShow the help.\n",np);
>
> ^^^^^^^^^
> You did not change this, but as we are here, ...
I wanted to leave as much code unchanged as possible (this /was/ my first
patch to btrfs-tools)
>
> > - printf("\n\t%s <cmd> --help\n\t\tShow detailed help for a command
> > or\n\t\t" + printf("\n\t%s <cmd> --help\n\t\tShow detailed help for a
> > command or"
>
> ^^^^^^^
> ... why not extending the general rule so that help messages will be
> printed with --help and -h?
We have to remember that this way we loose -h switch, quite intuitive to show
base 2 sizes with `btrfs file df`...
--
Hubert
next prev parent reply other threads:[~2011-07-12 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 12:39 [PATCH 1/2] add advanced use of --help to help message Hubert Kario
2011-01-23 12:42 ` [PATCH 2/2] add detailed help messages to btrfs command Hubert Kario
2011-01-23 14:07 ` Goffredo Baroncelli
2011-01-23 14:26 ` Helmut Hullen
2011-01-23 14:43 ` Felix Blanke
2011-01-23 14:28 ` Hubert Kario
2011-01-23 14:54 ` Goffredo Baroncelli
2011-01-23 15:06 ` Hubert Kario
2011-07-11 15:13 ` Jan Schmidt
2011-07-11 18:38 ` Goffredo Baroncelli
2011-07-11 19:11 ` Jan Schmidt
2011-07-11 20:35 ` Goffredo Baroncelli
2011-07-11 22:22 ` Hugo Mills
2011-07-12 10:49 ` Hubert Kario
2011-07-12 10:40 ` Hubert Kario [this message]
2011-07-12 10:43 ` Hugo Mills
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=201107121240.06740.kario@wit.edu.pl \
--to=kario@wit.edu.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).