From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Peter Wang <novalazy@gmail.com>, notmuch@notmuchmail.org
Subject: Re: search summary and exclusions
Date: Tue, 29 May 2012 08:00:00 -0700 [thread overview]
Message-ID: <87fwajnibz.fsf@servo.finestructure.net> (raw)
In-Reply-To: <20120529140107.GE2347@hili.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
On Mon, May 28 2012, Peter Wang <novalazy@gmail.com> wrote:
> % ./notmuch search --format=json --exclude=true -- thread:0000000000009598 tag:unread
> [{"thread": "0000000000009598",
> "timestamp": 1338231998,
> "date_relative": "Today 05:06",
> "matched": 1,
> "total": 15,
> "authors": "Mark Walters| Peter Wang",
> "subject": "[PATCH v6 3/6] cli: make --entire-thread=false work for format=json.",
> "tags": ["deleted", "draft", "replied", "sent", "unread"]}]
>
> Here is a thread I participated in. From this, my MUA displays "1/15",
> suggesting that there is 1 unread message out of a total of 15. But
> upon opening the thread, there are only 11 messages visible: 4 were
> drafts (possibly deleted) which have been excluded. To the user, it
> looks like some messages went missing.
>
> Therefore I would like search --output=summary --exclude=true
> to report the total number of non-excluded messages. It doesn't need to
> be via the "total" field; a new field would be fine.
What you have pasted above is --output=json, not --output=summary. The
formats are quite different. What are you asking for a change in?
But regardless, I don't think I would like to see the changes you
suggest. I would like for the thread total to list the total number of
messages in the thread, regardless whether they're excluded or not.
Same for the tags. I think I want to continue to see if excluded
messages are in a returned thread. The desire to hide the excluded
messages in the output is why they're marked as hidden/not visible.
Think about the excludes as acting on the search itself, and less on the
output. We exclude messages from search, but if they show up in a
returned thread we at least acknowledge that they're there.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-05-29 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 14:00 search summary and exclusions Peter Wang
2012-05-28 17:03 ` Jameson Graef Rollins
2012-05-29 4:01 ` Peter Wang
2012-05-29 8:37 ` Mark Walters
2012-05-29 15:00 ` Jameson Graef Rollins [this message]
2012-05-30 3:07 ` Peter Wang
2012-05-30 3:58 ` Jameson Graef Rollins
2012-05-30 7:49 ` Mark Walters
2012-06-17 7:03 ` Peter Wang
2012-06-17 7:22 ` Mark Walters
2012-06-17 7:27 ` [WIP 1/2] lib: add --exclude=all option Mark Walters
2012-06-17 7:27 ` [WIP 2/2] cli: add --exclude=all option to notmuch-search.c Mark Walters
2012-05-28 18:54 ` search summary and exclusions 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=87fwajnibz.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
--cc=novalazy@gmail.com \
/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).