From: Jani Nikula <jani@nikula.org>
To: Tomi Ollila <tomi.ollila@iki.fi>, John Lenz <lenz@math.uic.edu>,
notmuch@notmuchmail.org
Subject: Re: cli: add --include-html option to notmuch show
Date: Sat, 24 Aug 2013 13:59:20 +0300 [thread overview]
Message-ID: <878uzrnylz.fsf@nikula.org> (raw)
In-Reply-To: <m2wqni7swv.fsf@guru.guru-group.fi>
On Sun, 18 Aug 2013, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> Now, if we have --include-html should it be like that or
> --include-html=(true|false). Currently we have both cases, adding
> --verify, --decrypt, --create-folder, --batch, -no-hooks to the
> set... I cannot get a clear opinion (without wast^H^H^H^H spending
> excessive amount of time figuring these out) how this should be,
> therefore I'm inclined to the opinion that
>
> the current patch from John with simple --include-html could be applied,
> and in the future (if it is of anyone's interest) we update the parser
> allowing boolean --arg equal --arg=true. Then it is just how we decide
> to document these...
The argument parser we have allows NOTMUCH_OPT_BOOLEAN options to be
specified as --foo=(true|false) or simply --foo (for true). It is
already now just a matter of documentation, and I'm sure we're not
consistent.
We also have things like --no-hooks in notmuch new. I added that, and in
retrospect, that should be just --hooks=(true|false). I guess we left it
like that because the default is true. Perhaps we should amend the
argument parser to look for boolean option --foo if it encounters a
--no-foo option.
Why notmuch show has --exclude=(true|false) as a keyword option I don't
quite grasp; the --entire-thread option at least has a special
default. It might help some options if the parser had a way to tell if
it's seen some option or not.
Of course, none of this is really relevant to the patch in question!
BR,
Jani.
next prev parent reply other threads:[~2013-08-24 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 0:19 cli: add --include-html option to notmuch show John Lenz
2013-07-21 20:23 ` Tomi Ollila
2013-07-22 16:49 ` John Lenz
2013-07-25 2:36 ` John Lenz
2013-08-04 19:47 ` Tomi Ollila
2013-08-17 15:52 ` John Lenz
2013-08-18 11:25 ` Jani Nikula
2013-08-18 18:30 ` Tomi Ollila
2013-08-24 8:11 ` Mark Walters
2013-08-24 10:59 ` Jani Nikula [this message]
2013-08-24 15:29 ` [PATCH 1/1] test: test notmuch show --include-html option Tomi Ollila
2013-08-24 21:36 ` Mark Walters
2013-08-27 11:04 ` David Bremner
2013-08-27 11:03 ` cli: add --include-html option to notmuch show David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878uzrnylz.fsf@nikula.org \
--to=jani@nikula.org \
--cc=lenz@math.uic.edu \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).