From: Mark Walters <markwalters1009@gmail.com>
To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
Subject: Re: [PATCH v6 6/7] cli: search: Add --output=count
Date: Sun, 02 Nov 2014 09:29:28 +0000 [thread overview]
Message-ID: <87d2963q87.fsf@qmul.ac.uk> (raw)
In-Reply-To: <87bnoqbexm.fsf@steelpick.2x.cz>
Hi
On Sun, 02 Nov 2014, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> On Sat, Nov 01 2014, Mark Walters wrote:
>> On Fri, 31 Oct 2014, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
>>> This output can be used with --output=recipients or --output=sender
>>> and in addition to the addresses, it prints how many times was each
>>> address encountered during search.
>>
>> Hi
>>
>> I have a couple comments on this patch.
>>
>>> ---
>>> completion/notmuch-completion.bash | 2 +-
>>> completion/notmuch-completion.zsh | 2 +-
>>> doc/man1/notmuch-search.rst | 9 +++++--
>>> notmuch-search.c | 51 ++++++++++++++++++++++++++++++++------
>>> 4 files changed, 52 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/completion/notmuch-completion.bash b/completion/notmuch-completion.bash
>>> index cfbd389..39cd829 100644
>>> --- a/completion/notmuch-completion.bash
>>> +++ b/completion/notmuch-completion.bash
>>> @@ -294,7 +294,7 @@ _notmuch_search()
>>> return
>>> ;;
>>> --output)
>>> - COMPREPLY=( $( compgen -W "summary threads messages files tags sender recipients" -- "${cur}" ) )
>>> + COMPREPLY=( $( compgen -W "summary threads messages files tags sender recipients count" -- "${cur}" ) )
>>> return
>>> ;;
>>> --sort)
>>> diff --git a/completion/notmuch-completion.zsh b/completion/notmuch-completion.zsh
>>> index 3e52a00..d7e5a5e 100644
>>> --- a/completion/notmuch-completion.zsh
>>> +++ b/completion/notmuch-completion.zsh
>>> @@ -53,7 +53,7 @@ _notmuch_search()
>>> '--max-threads=[display only the first x threads from the search results]:number of threads to show: ' \
>>> '--first=[omit the first x threads from the search results]:number of threads to omit: ' \
>>> '--sort=[sort results]:sorting:((newest-first\:"reverse chronological order" oldest-first\:"chronological order"))' \
>>> - '--output=[select what to output]:output:((summary threads messages files tags sender recipients))'
>>> + '--output=[select what to output]:output:((summary threads messages files tags sender recipients count))'
>>> }
>>>
>>> _notmuch()
>>> diff --git a/doc/man1/notmuch-search.rst b/doc/man1/notmuch-search.rst
>>> index 42f17e4..ec89200 100644
>>> --- a/doc/man1/notmuch-search.rst
>>> +++ b/doc/man1/notmuch-search.rst
>>> @@ -96,9 +96,14 @@ Supported options for **search** include
>>> Like **sender** but for addresses from *To*, *Cc* and
>>> *Bcc* headers.
>>>
>>> + **count**
>>> + Can be used in combination with **sender** or
>>> + **recipients** to print the count of how many times was
>>> + the address encountered during search.
>>> +
>>> This option can be given multiple times to combine different
>>> - outputs. Currently, this is only supported for **sender** and
>>> - **recipients** outputs.
>>> + outputs. Currently, this is only supported for **sender**,
>>> + **recipients** and **count** outputs.
>>
>> It might be worth saying that the results will be slower if count is
>> specified.
>
> I wrote something like this in
> id:1414889400-30977-10-git-send-email-sojkam1@fel.cvut.cz.
>
>>
>>> ``--sort=``\ (**newest-first**\ \|\ **oldest-first**)
>>
>> I think sort works as expected if count is not specified, but does not
>> with count.
>
> Agreed.
>
>> Maybe count can be done by doing two passes?
>
> What do you mean by pass?
I mean iterating through the messages twice: so the first time would
fill in the count in the hash map, and the second iteration would print
the addresses.
Best wishes
Mark
>
>> If it is difficult it might be sufficient to just document that sort
>> has no effect.
>
> I'd do it this way :)
>
> Thanks,
> -Michal
next prev parent reply other threads:[~2014-11-02 9:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:53 [PATCH v6 0/7] notmuch search --output=sender/recipients Michal Sojka
2014-10-31 21:53 ` [PATCH v6 1/7] cli: search: Refactor passing of command line options Michal Sojka
2014-10-31 21:53 ` [PATCH v6 2/7] cli: Add support for parsing keyword-flag arguments Michal Sojka
2014-10-31 21:53 ` [PATCH v6 3/7] cli: search: Convert --output to keyword-flag argument Michal Sojka
2014-10-31 21:53 ` [PATCH v6 4/7] cli: search: Add --output={sender,recipients} Michal Sojka
2014-11-01 7:14 ` David Bremner
2014-10-31 21:53 ` [PATCH v6 5/7] cli: search: Do not output duplicate addresses Michal Sojka
2014-10-31 21:54 ` [PATCH v6 6/7] cli: search: Add --output=count Michal Sojka
2014-11-01 1:16 ` Mark Walters
2014-11-02 0:53 ` Michal Sojka
2014-11-02 9:29 ` Mark Walters [this message]
2014-11-02 9:34 ` Michal Sojka
2014-11-03 9:44 ` Tomi Ollila
2014-11-03 21:39 ` Michal Sojka
2014-10-31 21:54 ` [PATCH v6 7/7] cli: search: Add --filter-by option to configure address filtering Michal Sojka
2014-11-01 8:55 ` Jani Nikula
2014-11-01 9:21 ` Michal Sojka
2014-11-01 11:30 ` [RFC PATCH 0/2] cli: split 'notmuch address' from 'notmuch search' Jani Nikula
2014-11-01 11:30 ` [RFC PATCH 1/2] cli: add support for hierarchical command line option arrays Jani Nikula
2014-11-01 11:30 ` [RFC PATCH 2/2] cli: add notmuch address command Jani Nikula
2014-11-04 9:14 ` [RFC PATCH 0/2] cli: split 'notmuch address' from 'notmuch search' Mark Walters
2014-11-01 0:22 ` [PATCH v6 0/7] notmuch search --output=sender/recipients Mark Walters
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=87d2963q87.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/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).