unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH] cli: add support for only printing the addresses in notmuch address
Date: Wed, 20 Dec 2017 09:02:01 +0200	[thread overview]
Message-ID: <873745vq52.fsf@nikula.org> (raw)
In-Reply-To: <878tdy8a2q.fsf@ligo.caltech.edu>

On Tue, 19 Dec 2017, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Tue, Dec 19 2017, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>> On Tue 2017-12-19 13:23:55 -0800, Jameson Graef Rollins wrote:
>>> On Thu, Nov 02 2017, Jani Nikula <jani@nikula.org> wrote:
>>>> The notmuch address output is much more useful for scripts with just
>>>> the addresses printed. Support this using the --output=address option.
>>>
>>> Isn't "address" kind of orthogonal to "sender" and "recipient"?  Isn't
>>> this more like the --output/--format distinction in search?
>>
>> i think i agree with Jamie here -- it'd be nice to be able to ask for
>> the addresses of the senders, or the addresses of the recipients.  how
>> would that be done here?
>
> Sorry, I see now that address already has the --format option with the
> expected values.  So I think either address-only or sender/recipient
> should be a separate option.

Note that you can give the notmuch address --output option multiple
times to control the output. For example,

~$ notmuch address --output=sender --output=recipients id:878tdy8a2q.fsf@ligo.caltech.edu
Jameson Graef Rollins <jrollins@finestructure.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Jani Nikula <jani@nikula.org>
notmuch@notmuchmail.org

~$ notmuch address --output=recipients --output=address id:878tdy8a2q.fsf@ligo.caltech.edu
dkg@fifthhorseman.net
jani@nikula.org
notmuch@notmuchmail.org

~$ 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.

notmuch search uses separate --entire-thread, --body, and --include-html
options, and I think those are getting messy.

BR,
Jani.

  reply	other threads:[~2017-12-20  7:02 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 [this message]
2017-12-20  7:16         ` Jameson Graef Rollins
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=873745vq52.fsf@nikula.org \
    --to=jani@nikula.org \
    --cc=dkg@fifthhorseman.net \
    --cc=jrollins@finestructure.net \
    --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).