From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH] notes: attach help text to subcommands
Date: Fri, 8 Jun 2012 17:54:23 +0200 [thread overview]
Message-ID: <CAMP44s28aoKkXyTr4Stow-empen9_CUxAWTDi_gcSUpKjMzg6Q@mail.gmail.com> (raw)
In-Reply-To: <20120608153607.GC10380@burratino>
On Fri, Jun 8, 2012 at 5:36 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Ramkumar Ramachandra wrote:
>
>> Thanks. I wish we could do something aout USAGE_OPTS_WIDTH and
>> USAGE_GAP; I stole them from parse-options.
>
> Expose them in parse-options.h? Or put this functionality in a
> parseopt-related file?
>
> Copy+paste must die. :)
There's many commands that would benefit from this. In addition to
provide a better help for subcommands, this can be used to generate
automatically the shell completion list of subcommands.
Even more; in zsh it would be possible to show this help text directly
in the completion.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2012-06-08 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 9:35 [RFC/PATCH] parse-options: introduce parse_subcommands Ramkumar Ramachandra
2012-06-04 17:01 ` Junio C Hamano
2012-06-06 14:10 ` Ramkumar Ramachandra
2012-06-06 17:26 ` Junio C Hamano
2012-06-08 8:56 ` [RFC] notes: attach help text to subcommands Ramkumar Ramachandra
2012-06-08 14:49 ` Junio C Hamano
2012-06-08 15:28 ` [PATCH] " Ramkumar Ramachandra
2012-06-08 15:36 ` Jonathan Nieder
2012-06-08 15:54 ` Felipe Contreras [this message]
2012-06-08 16:34 ` Ramkumar Ramachandra
2012-06-13 15:04 ` Felipe Contreras
2012-06-08 17:03 ` Junio C Hamano
2012-06-05 23:32 ` [RFC/PATCH] parse-options: introduce parse_subcommands Jonathan Nieder
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=CAMP44s28aoKkXyTr4Stow-empen9_CUxAWTDi_gcSUpKjMzg6Q@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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 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).