Re: [PATCH] emacs: wash: make word-wrap bound message width

[notmuch-archives.git] / 22 / bc2026af2d779180ae21304f40a9809a7aeb5f

Return-Path: <amdragon@mit.edu>\r
X-Original-To: notmuch@notmuchmail.org\r
Delivered-To: notmuch@notmuchmail.org\r
Received: from localhost (localhost [127.0.0.1])\r
        by olra.theworths.org (Postfix) with ESMTP id 93F8B429E54\r
        for <notmuch@notmuchmail.org>; Sun, 22 Jan 2012 17:52:52 -0800 (PST)\r
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
X-Spam-Flag: NO\r
X-Spam-Score: -0.7\r
X-Spam-Level: \r
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
        tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
Received: from olra.theworths.org ([127.0.0.1])\r
        by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
        with ESMTP id JHLrpsoEFr7k for <notmuch@notmuchmail.org>;\r
        Sun, 22 Jan 2012 17:52:51 -0800 (PST)\r
Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU\r
        [18.9.25.13])\r
        by olra.theworths.org (Postfix) with ESMTP id 9DF2B429E40\r
        for <notmuch@notmuchmail.org>; Sun, 22 Jan 2012 17:52:51 -0800 (PST)\r
X-AuditID: 1209190d-b7fbf6d0000008ba-14-4f1cbd72f71d\r
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36])\r
        by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP\r
        id ED.BA.02234.27DBC1F4; Sun, 22 Jan 2012 20:52:50 -0500 (EST)\r
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
        by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id q0N1qoIb008721; \r
        Sun, 22 Jan 2012 20:52:50 -0500\r
Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
        (authenticated bits=0)\r
        (User authenticated as amdragon@ATHENA.MIT.EDU)\r
        by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0N1qnCf024532\r
        (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
        Sun, 22 Jan 2012 20:52:50 -0500 (EST)\r
Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
        (envelope-from <amdragon@MIT.EDU>)\r
        id 1Rp954-00027G-71; Sun, 22 Jan 2012 20:52:22 -0500\r
Date: Sun, 22 Jan 2012 20:52:22 -0500\r
From: Austin Clements <amdragon@MIT.EDU>\r
To: Mark Walters <markwalters1009@gmail.com>\r
Subject: Re: [PATCH] Automatically exclude tags in notmuch-show\r
Message-ID: <20120123015222.GB7600@mit.edu>\r
References: <874nvric7c.fsf@qmul.ac.uk>\r
        <1327010583-23954-1-git-send-email-markwalters1009@gmail.com>\r
        <20120119225910.GT16740@mit.edu> <871uqvgrnm.fsf@qmul.ac.uk>\r
        <20120120171801.GA16740@mit.edu> <20120122181609.GQ16740@mit.edu>\r
        <87zkdfgr0m.fsf@qmul.ac.uk>\r
MIME-Version: 1.0\r
Content-Type: text/plain; charset=us-ascii\r
Content-Disposition: inline\r
In-Reply-To: <87zkdfgr0m.fsf@qmul.ac.uk>\r
User-Agent: Mutt/1.5.21 (2010-09-15)\r
X-Brightmail-Tracker:\r
 H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42IRYrdT0S3aK+NvcG65jcXquTwW12/OZHZg\r
        8tg56y67x7NVt5gDmKK4bFJSczLLUov07RK4Mq4u62MseGxSceTqL9YGxouaXYycHBICJhJ7\r
        npxmhrDFJC7cW8/WxcjFISSwj1Hi27nfjBDOBkaJyzeuQ2VOMkn0TdjIDuEsYZSY9/IxUxcj\r
        BweLgKrEmxf1IKPYBDQktu1fzghiiwjoSNw+tIAdxGYWkJb49ruZCcQWFrCXmLx0MdhqXgFt\r
        if62e2D1QgI9TBKL9xRCxAUlTs58wgLRqyVx499LsFUgc5b/4wAJcwKtargwB2ykqICKxJST\r
        29gmMArNQtI9C0n3LITuBYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3SN9HIzS/RSU0o3MYKC\r
        mlOSdwfju4NKhxgFOBiVeHgjlsr4C7EmlhVX5h5ilORgUhLl7d0DFOJLyk+pzEgszogvKs1J\r
        LT7EKMHBrCTC6/xZ2l+INyWxsiq1KB8mJc3BoiTOq6r1zk9IID2xJDU7NbUgtQgmK8PBoSTB\r
        ew5kqGBRanpqRVpmTglCmomDE2Q4D9Dw3yA1vMUFibnFmekQ+VOMuhxffredZxRiycvPS5US\r
        55UFphMhAZCijNI8uDmwZPSKURzoLWHe7yCjeICJDG7SK6AlTEBLOPKkQJaUJCKkpBoYz3pY\r
        3b39PD71gm75limfuaYH7Pz/InbR1w23TsyVX/NkPd+SS/f99R1E2/pMDjjsqj9r/Tj3nXju\r
        wc/TO3ynGU2NWcys1b1u9TmudWtydib8f3tJaNmTD59Fgr5u/p9w368pV9bPr9hnae/zZpe9\r
        J/iu/Evnc/NL6kzj8/wRs7f/rI3vsxpFbiWW4oxEQy3mouJEAN9mOBghAwAA\r
Cc: notmuch@notmuchmail.org\r
X-BeenThere: notmuch@notmuchmail.org\r
X-Mailman-Version: 2.1.13\r
Precedence: list\r
List-Id: "Use and development of the notmuch mail system."\r
        <notmuch.notmuchmail.org>\r
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
        <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
List-Post: <mailto:notmuch@notmuchmail.org>\r
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
        <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
X-List-Received-Date: Mon, 23 Jan 2012 01:52:52 -0000\r
\r
Quoth Mark Walters on Jan 23 at  1:13 am:\r
> On Sun, 22 Jan 2012 13:16:09 -0500, Austin Clements <amdragon@MIT.EDU> wrote:\r
> > Quoth myself on Jan 20 at 12:18 pm:\r
> > > Quoth Mark Walters on Jan 20 at 12:10 am:\r
> > > > \r
> > > > Ok Having said this is trivial I have found a problem. What should\r
> > > > notmuch do if you do something like\r
> > > > \r
> > > > notmuch show id:<some-id>\r
> > > > and that message is marked with a deleted tag? To be consistent with the\r
> > > > other cases (where a deleted message is in a matched thread) we might\r
> > > > want to return the message with the not-matched flag set (eg in\r
> > > > JSON). But my patch doesn't, as it never even sees the thread since it\r
> > > > doesn't match.\r
> > > > \r
> > > > Looking at notmuch-show.c I think we should not apply the exclude tags\r
> > > > to do_show_single, but usually should apply it to do_show. One solution\r
> > > > which is simple and is at least close to right would be to get do_show\r
> > > > to return the number of threads found. If this is zero then retry the\r
> > > > query without the excludes (possible setting the match_flag to zero on\r
> > > > each message since we know it does not match)\r
> > > > \r
> > > > This is not a completely correct solution as if you ask notmuch-show to\r
> > > > show more than one thread it might  threads which only contain deleted\r
> > > > messages.\r
> > > > \r
> > > > I can't see other good possibilities without slowing down the normal\r
> > > > path a lot (eg find all threads that match the original query and then\r
> > > > apply the argument above).\r
> > > > \r
> > > > Any thoughts?\r
> > > \r
> > > Oh dear.\r
> > > \r
> > > Well, here's one idea.  Instead of doing a single thread query in\r
> > > show, do a thread query without the exclusions and then a message\r
> > > query with the exclusions.  Output all of the messages from the first\r
> > > query, but use the results of the second query to determine which\r
> > > messages are "matched".  The same could be accomplished in the library\r
> > > somewhat more efficiently, but it's not obvious to me what the API\r
> > > would be.\r
> > \r
> > Here's a slightly crazier idea that's more library-invasive than the\r
> > original approach, but probably better in the long run.\r
> > \r
> > Have notmuch_query_search_* return everything and make exclusion a\r
> > message flag like NOTMUCH_MESSAGE_FLAG_MATCH.  Tweak the definition of\r
> > "matched" to mean "matched and not excluded" (specifically, a message\r
> > would have the match flag or the excluded flag or neither, but not\r
> > both).  Search would skip threads with zero matched messages and I\r
> > think show would Just Work.\r
> > \r
> > I can think of two ways to implement this.  notmuch_query_search_*\r
> > could perform both the original query and the query with exclusions\r
> > and use the docid set from the second to compute the "excluded"\r
> > message flag.  Alternatively, it could examine the tags of each\r
> > message directly to compute the flag.  The latter is probably easier\r
> > to implement, but probably slower.\r
> > \r
> > Thoughts?\r
> \r
> I have now thought about this some more and think I understand your idea\r
> (and how it would work) rather better now. \r
> \r
> I would suggest one small change: the flags for the messages returned\r
> should be "independent": so a message can match the query or not, and it\r
> can be excluded or not, with all 4 combinations being possible. (The\r
> consumer of notmuch_query_search_* would extract the information it\r
> wanted.)\r
\r
I'd initially approached it this way, but went with redefining a\r
"matched" messages because it had much less impact on the API.  For\r
example, with the redefined "match",\r
notmuch_thread_get_matched_messages still does the right thing for\r
search and things like the thread subject can still be based on\r
"matched" messages.  If we orthongonalize these flags, then we at\r
least need to count matched non-excluded messages and provide an API\r
to access this (while I don't have a solid argument against such an\r
API it just seems weirdly specific to me).\r
\r
My other concern is performance.  In thread queries, marking\r
non-matched messages as excluded would require either an extra query\r
per thread or a single query to match all excluded messages (not\r
filtered by the primary query).  The former is prohibitive, though the\r
latter might be acceptable (that might depend on how many things\r
people mark as spam or deleted).  If the cost is too high, this\r
suggests that we shouldn't mark non-matched messages as excluded, but\r
then we're back to effectively having three levels of matching: not\r
matched, matched but not excluded, and matched but excluded.\r
\r
> I have thought about some implementation ideas but I think sorting is\r
> going to be the deciding factor: what order should\r
> notmuch_query_search_* return messages/threads? \r
\r
Yes.  This is exactly what I've been puzzling over, too.\r
\r
> For notmuch_query_search_messages either it returns them all together\r
> with the excluded messages marked, or returns all included ones, and\r
> then all excluded one.\r
\r
I would prefer them intermingled.  I feel like returning one and then\r
the other is just exposing implementation details.  Plus, it's unclear\r
if the order of the two groups should depend on the sort order, be\r
configurable, or what.  Intermingling them seems like the obvious\r
answer.\r
\r
> For notmuch_query_search_threads it is less clear. Currently it returns\r
> threads in order of first matching message. It is not clear what\r
> matching means now: is matching and included, or just matching? If the\r
> former then we will be returning some threads with no matching and\r
> included messages so we need to decide where to put them in the order.\r
\r
I would argue that, if the caller cares about the sort order of the\r
results, it only makes sense for it to skip over threads consisting\r
only of excluded messages, and if the caller doesn't care about the\r
sort order, we can choose whatever's most convenient.\r
\r
> If we sort in both cases just on matching then we have the same\r
> output/sort as notmuch pre-excluded flags, just the frontends\r
> notmuch-search/show can decide to omit some lines/results. Note that\r
> after omitting "excluded" lines the thread sort would be different from\r
> the current notmuch-with-excluded implementation.\r
> \r
> Whereas if we sort based on matching and included, we keep the current\r
> sort order with some stuff appended.\r
> \r
> As regards implementation I think notmuch_query_search_messages is the\r
> crucial place: once that returns one of its two orders the rest sort of\r
> takes care of itself.\r
\r
I think that comes down to exactly how we want to handle the message\r
flags.\r
\r
> Best wishes\r
> \r
> Mark\r