From: Andrew Horton <andrew.j.horton@gmail.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-user@gnu.org
Subject: Re: getopt-long
Date: Mon, 5 Dec 2011 20:00:01 +0000 [thread overview]
Message-ID: <CAGE+M9RozH2AGu5WSsB1N2piz-zbpGQ4oeaFSgZ9HXYDPf2taA@mail.gmail.com> (raw)
In-Reply-To: <87wraa988g.fsf@ambire.localdomain>
That would do the trick. I've also thought that a (help "...") for
each option would also be useful, which could append the string for
each arg to the "--help" option text automatically (somehow).
On 5 December 2011 18:35, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () Andrew Horton <andrew.j.horton@gmail.com>
> () Thu, 01 Dec 2011 11:40:40 +0000
>
> recognize multiple use of an option when using getopt-long.
>
> Guile 1.4.x extended (ice-9 getopt-long) to handle multiple occurances.
> Here is an excerpt from (info "(guile) getopt-long Reference"):
>
> `(merge-multiple? BOOL)'
> If BOOL is `#t' and the `value' property is not `#f', all
> (one or multiple) occurrances are merged into a list with
> order retained. If `#f', each instance of the option results
> in a separate entry in the resulting alist.
>
> Subsequently, this rat jumped to the non-(not-yet?)-sinking ttn-do
> as module ‘(ttn-do zzz bamboozled)’. More info online:
>
> http://www.gnuvola.org/software/guile/doc/getopt_002dlong-Reference.html
> http://www.gnuvola.org/software/ttn-do/ttn-do.html.gz#zzz-bamboozled
>
> I think it would be cool if this were to find berth in official Guile.
next prev parent reply other threads:[~2011-12-05 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 11:40 getopt-long Andrew Horton
2011-12-05 17:14 ` getopt-long Ludovic Courtès
2011-12-05 20:50 ` getopt-long Andy Wingo
2011-12-05 18:35 ` getopt-long Thien-Thi Nguyen
2011-12-05 20:00 ` Andrew Horton [this message]
2011-12-05 20:51 ` getopt-long Andy Wingo
2011-12-05 21:57 ` getopt-long Ludovic Courtès
2011-12-06 14:13 ` getopt-long Thien-Thi Nguyen
2011-12-06 16:10 ` getopt-long Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGE+M9RozH2AGu5WSsB1N2piz-zbpGQ4oeaFSgZ9HXYDPf2taA@mail.gmail.com \
--to=andrew.j.horton@gmail.com \
--cc=guile-user@gnu.org \
--cc=ttn@gnuvola.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).