Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id E6EC46DE0924 for ; Sat, 18 Jul 2015 02:11:45 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.719 X-Spam-Level: X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[AWL=0.101, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGMlil-czEyr for ; Sat, 18 Jul 2015 02:11:44 -0700 (PDT) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by arlo.cworth.org (Postfix) with ESMTPS id BC8C26DE0352 for ; Sat, 18 Jul 2015 02:11:43 -0700 (PDT) Received: by widjy10 with SMTP id jy10so57364541wid.1 for ; Sat, 18 Jul 2015 02:11:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=Lr6RFOEnf3Nfj985VwhUat0pxm9i34hMr+vBtAZY/Yg=; b=iF2xBOES2Q9Vg9F2Ri7ykN+tWLjAWI39E+l3bhiWq0mZbXtJCkwzVAPLvNUsydOXBI YmVPkKhm3sE5qwQziuTN9IHBYtR1R1grIUTTrfpzBdUnhNvH/gWIGqTlZEfBTvaYO+NF Oo0pdFrqYiC9hsKQU89J5cARAI066qNgYWEC+cvd1LNqIPPiO/Y8XrBoaaheD6PElbWN kMUolfXausfZUFxTwq/yGB8Tai5D4HEw8WT3MxPX7/IBMn29RL1I6iQn7+uMK0ne8P+s yv+0AUqpSw2os8G2R+yBk8Z6qvEY9+xLLaUNWPon5ktPB3mp581r5OnxR0tMhWZa+eHG IcmQ== X-Received: by 10.194.178.1 with SMTP id cu1mr37842626wjc.59.1437210701678; Sat, 18 Jul 2015 02:11:41 -0700 (PDT) Received: from chitra.no-ip.org (ip82-139-115-46.lijbrandt.net. [82.139.115.46]) by smtp.gmail.com with ESMTPSA id ju2sm1648603wid.12.2015.07.18.02.11.40 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Jul 2015 02:11:41 -0700 (PDT) Sender: Suvayu Ali Date: Sat, 18 Jul 2015 11:11:39 +0200 From: Suvayu Ali To: notmuch@notmuchmail.org Subject: Re: Searching for phrases in the body of an email Message-ID: <20150718091139.GB8311@chitra.no-ip.org> Mail-Followup-To: notmuch@notmuchmail.org References: <20150717121111.GF25651@chitra.no-ip.org> <55A923E9.5070509@imca-cat.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55A923E9.5070509@imca-cat.org> User-Agent: Mutt/1.5.23.1 (2014-03-12) X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jul 2015 09:11:46 -0000 Hi Lewis, On Fri, Jul 17, 2015 at 10:48:57AM -0500, J. Lewis Muir wrote: > > 1. Perhaps you are remembering the "no plain text" message incorrectly? > For example, the message could have referred to "text/plain" or > "plaintext" (no space). These would be sufficiently different to not > match your grep pattern. True, but my puzzlement is notmuch shouldn't return those results in the first place, since I provided a quoted string: "plain text", unless of course I need to escape the quotes. Okay, just checked it, doesn't make a difference in the number of hits from notmuch. > 2. Perhaps your email client rendered the "no plain text" message when > it encountered an email with only a "text/html" content type? In > this case, the "no plain text" (or whatever) message would not be > present in the email itself since it would be generated by the email > client when rendering the email. This is possible, but I use mutt. As far as I know, it doesn't do "smart" things like that. I also recall looking at the mime parts individually as I was surprised at the behaviour, and it was indeed a useless text/plain part with that message. > 3. A really long shot, but could a line wrap have occurred after "plain" > such that "text" appeared on the next line? Your grep pattern would > not match that. Good point, I tried grepping for this instead: 'plain[[:space:]/]+text', no luck. Thanks for your comments. Cheers, -- Suvayu Open source is the future. It sets us free.