From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/5] Move to --with-excluded approach to excludes
Date: Sat, 10 Mar 2012 17:19:33 -0800 [thread overview]
Message-ID: <87399g7x3u.fsf@servo.finestructure.net> (raw)
In-Reply-To: <1330779918-28024-1-git-send-email-markwalters1009@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2976 bytes --]
On Sat, 3 Mar 2012 13:05:13 +0000, Mark Walters <markwalters1009@gmail.com> wrote:
> This series implements the proposal in id:"87y5riuz7v.fsf@qmul.ac.uk"
> to move to a consistent --with-excluded approach rather than the
> previous --no-exclude approach. See the message there and its
> descendants for discussion.
>
> The main user side change is that notmuch-search no longer defaults to
> showing all the excluded threads with [0/n] but will do so if the user
> says they want all the messages (i.e., by specifying --with-excluded).
>
> However, it makes everything consistent throughout the commandline and
> lib interfaces. In all cases a "message" type search only returns the
> non-excluded matches (unless --with-excluded is specified) and a
> "thread" type search returns all messages (including excluded ones) in
> threads that match in a non-excluded message.
Hi, Mark. Thanks so much for working on this. This new solution seems
like a good one. It keeps the default as expected (excluded are
actually excluded from all output), and the with-excluded option behaves
intuitively. Looks good to me.
Unfortunately, as I discussed with you on irc today, there seems to be a
problem with the patch series that is preventing it from working as
expected. The outputs of the following commands should agree, which
they do:
servo:~/src/notmuch/git [master] 0$ ./notmuch count --with-excluded tag:inbox
51171
servo:~/src/notmuch/git [master] 0$ ./notmuch search --output=messages --with-excluded tag:inbox | wc -l
51171
servo:~/src/notmuch/git [master] 0$
However, they should also agree in this case, which they don't:
servo:~/src/notmuch/git [master] 0$ ./notmuch count tag:inbox
115
servo:~/src/notmuch/git [master] 0$ ./notmuch search --output=messages tag:inbox | wc -l
51169
servo:~/src/notmuch/git [master] 0$
In this last case, notmuch search is outputting (some but not all(!))
excluded messages when it shouldn't be. However, if I use a more
complicated search term, everything seems to be working fine:
servo:~/src/notmuch/git [master] 0$ ./notmuch count tag:inbox and tag:unread
0
servo:~/src/notmuch/git [master] 0$ ./notmuch search --output=messages tag:inbox and tag:unread | wc -l
0
servo:~/src/notmuch/git [master] 0$ ./notmuch count --with-excluded tag:inbox and tag:unread
47245
servo:~/src/notmuch/git [master] 0$ ./notmuch search --output=messages --with-excluded tag:inbox and tag:unread | wc -l
47245
servo:~/src/notmuch/git [master] 0$
It also works if I give a single "from:" search term instead of a single
"tag:" search term. So it appears to be something about how the
excluded query is constructed.
I can't figure out where the problem is, although I'm still looking. If
anyone else can figure it out, please let us know.
I would really like to get this series applied so that I can get back to
following master!
Thanks again for all the work.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2012-03-11 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 13:05 [PATCH 0/5] Move to --with-excluded approach to excludes Mark Walters
2012-03-03 13:05 ` [PATCH 1/5] lib: rename (and negate) set_omit_excluded set_with_excluded Mark Walters
2012-03-03 13:05 ` [PATCH 2/5] cli: move count to the new --with-excluded naming scheme Mark Walters
2012-03-03 13:05 ` [PATCH 3/5] cli: move search " Mark Walters
2012-03-03 13:05 ` [PATCH 4/5] cli: move show " Mark Walters
2012-03-03 13:05 ` [PATCH 5/5] emacs: make show set --with-excluded Mark Walters
2012-03-11 1:19 ` Jameson Graef Rollins [this message]
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=87399g7x3u.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=markwalters1009@gmail.com \
--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).