From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jani Nikula <jani@nikula.org>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] cli: add support for only printing the addresses in notmuch address
Date: Tue, 19 Dec 2017 23:16:16 -0800 [thread overview]
Message-ID: <87wp1hg98f.fsf@ligo.caltech.edu> (raw)
In-Reply-To: <873745vq52.fsf@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Wed, Dec 20 2017, Jani Nikula <jani@nikula.org> wrote:
> ~$ notmuch address --output=sender --output=recipients --output=address --output=count id:878tdy8a2q.fsf@ligo.caltech.edu
> 1 notmuch@notmuchmail.org
> 1 jrollins@finestructure.net
> 1 dkg@fifthhorseman.net
> 1 jani@nikula.org
>
> I prefer this to separate options.
Really? If each is just a switch then why not:
~$ notmuch address --sender --recipients --address --count id:878tdy8a2q.fsf@ligo.caltech.edu
? It's just shorter, right?
Also, this behavior is quite different than for search, in which only
the last --output applies.
> notmuch search uses separate --entire-thread, --body, and --include-html
> options, and I think those are getting messy.
The seem less messy than a "--output=" prefixed version of the same.
jamie.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-12-20 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 18:44 [PATCH] cli: add support for only printing the addresses in notmuch address Jani Nikula
2017-12-15 12:01 ` David Bremner
2017-12-19 21:23 ` Jameson Graef Rollins
2017-12-20 1:12 ` Daniel Kahn Gillmor
2017-12-20 1:25 ` Jameson Graef Rollins
2017-12-20 7:02 ` Jani Nikula
2017-12-20 7:16 ` Jameson Graef Rollins [this message]
2017-12-20 11:15 ` Jani Nikula
2017-12-20 16:41 ` Jameson Graef Rollins
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=87wp1hg98f.fsf@ligo.caltech.edu \
--to=jrollins@finestructure.net \
--cc=dkg@fifthhorseman.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.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.
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).