From: Mark Walters <markwalters1009@gmail.com>
To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
Subject: Re: [PATCH v5 0/7] notmuch search --output=sender/recipients
Date: Fri, 31 Oct 2014 08:54:38 +0000 [thread overview]
Message-ID: <878ujwvctt.fsf@qmul.ac.uk> (raw)
In-Reply-To: <1414713573-21461-1-git-send-email-sojkam1@fel.cvut.cz>
On Thu, 30 Oct 2014, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> Hi all,
>
> this is v5 of the search --output=address series. It obsoletes v4
> (id:1414421455-3037-1-git-send-email-sojkam1@fel.cvut.cz).
>
> I addresses comments from Mark and Tomi. Based on the comments to v4
> and earlier versions, patches 1-4 should be ready for merging. Patch 5
> is a non-controversial part of the controversial --filter-by patch and
> could be probably merged after review.
I have looked at Patches 1-5 and tested. These look good to me. +1
My only query is in the text output: should the name part be printed as
a quoted string. For example currently I get a line of the form
Bloggs, Fred <fred@example.com>
and I think in theory I could have a real name
"Fred <stupid> Bloggs" which this would print without the quotes.
For the other formats it is much less of a problem because the name and
address are clearly separated.
I am happy with an answer of the form "for robust parseable results use a
structured format" which is what we say for search for example.
I just thought I would mention it in case you thought the quoted form
was more useful for consumers.
Best wishes
Mark
>
> Patch 6 needs at least a review and patch 7 needs more discussion.
>
> Changes from v4:
>
> - patch changed to commit in commit messages
> - opt->format changed to format
> - Added comments to process_* functions
> - duplicite changed to duplicate
> - check_duplicate changed to is_duplicate
> - Deduplication was split into two commits: basic deduplication
> without a command line option and configurable deduplication with
> --fiter-by.
>
> Changes from v3:
>
> - `o' renamed to `opt'.
> - Conversion of --output from keyword to keyword-flags is now a
> separate patch.
> - Structured output formats print name and address separately.
> - Added test for --format=json.
> - Changed --filter-by default to nameaddr. In v2, the default was
> addrfold, in v3 the default was no filtering at all. I believe that
> Mark's suggestion to make nameaddr the default is good trade off.
> - Added new --output=count
> - Minor style fixes
> - Few typos fixed
> - There is no way to output unfiltered (duplicite) addresses.
> Hopefully, the introduction of --output=count is sufficient
> replacement for this "feature".
>
> Cheers,
> -Michal
>
>
> Jani Nikula (1):
> cli: Add support for parsing keyword-flag arguments
>
> Michal Sojka (6):
> cli: search: Refactor passing of command line options
> cli: search: Convert --output to keyword-flag argument
> cli: search: Add --output={sender,recipients}
> cli: search: Do not output duplicate addresses
> cli: search: Add --output=count
> cli: search: Add --filter-by option to configure address filtering
>
> command-line-arguments.c | 6 +-
> command-line-arguments.h | 1 +
> completion/notmuch-completion.bash | 8 +-
> completion/notmuch-completion.zsh | 4 +-
> doc/man1/notmuch-search.rst | 66 ++++++-
> notmuch-search.c | 388 +++++++++++++++++++++++++++++--------
> test/T090-search-output.sh | 137 +++++++++++++
> test/T095-search-filter-by.sh | 64 ++++++
> test/T410-argument-parsing.sh | 3 +-
> test/arg-test.c | 9 +
> 10 files changed, 604 insertions(+), 82 deletions(-)
> create mode 100755 test/T095-search-filter-by.sh
>
> --
> 2.1.1
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2014-10-31 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 23:59 [PATCH v5 0/7] notmuch search --output=sender/recipients Michal Sojka
2014-10-30 23:59 ` [PATCH v5 1/7] cli: search: Refactor passing of command line options Michal Sojka
2014-10-30 23:59 ` [PATCH v5 2/7] cli: Add support for parsing keyword-flag arguments Michal Sojka
2014-10-30 23:59 ` [PATCH v5 3/7] cli: search: Convert --output to keyword-flag argument Michal Sojka
2014-10-30 23:59 ` [PATCH v5 4/7] cli: search: Add --output={sender,recipients} Michal Sojka
2014-10-30 23:59 ` [PATCH v5 5/7] cli: search: Do not output duplicate addresses Michal Sojka
2014-10-30 23:59 ` [PATCH v5 6/7] cli: search: Add --output=count Michal Sojka
2014-10-30 23:59 ` [PATCH v5 7/7] cli: search: Add --filter-by option to configure address filtering Michal Sojka
2014-10-31 8:54 ` Mark Walters [this message]
2014-10-31 10:20 ` [PATCH v5 0/7] notmuch search --output=sender/recipients Mark Walters
2014-10-31 15:32 ` Michal Sojka
2014-10-31 16:46 ` Tomi Ollila
2014-10-31 16:54 ` Mark Walters
2014-10-31 16:47 ` Mark Walters
2014-10-31 15:03 ` Jesse Rosenthal
2014-10-31 15:43 ` Michal Sojka
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=878ujwvctt.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).