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 AA6D56DE02A6 for ; Thu, 19 May 2016 04:06:15 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.012 X-Spam-Level: X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[AWL=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UKhVWxkbeGgf for ; Thu, 19 May 2016 04:06:07 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 335B46DE024A for ; Thu, 19 May 2016 04:05:53 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1b3Llx-0008Lw-Be; Thu, 19 May 2016 07:05:45 -0400 Received: (nullmailer pid 6912 invoked by uid 1000); Thu, 19 May 2016 11:05:51 -0000 From: David Bremner To: Tomi Ollila , notmuch@notmuchmail.org Cc: tomi.ollila@iki.fi Subject: Re: [PATCH] cli: tell how many messages were precisely matched when expected 1 match In-Reply-To: <1462649058-5330-1-git-send-email-tomi.ollila@iki.fi> References: <1462649058-5330-1-git-send-email-tomi.ollila@iki.fi> User-Agent: Notmuch/0.22 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Thu, 19 May 2016 08:05:51 -0300 Message-ID: <87zirmwbn4.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Thu, 19 May 2016 11:06:15 -0000 Tomi Ollila writes: > In case of notmuch reply and notmuch show --part=N it is required that > search terms match to one message. If match count was != 1, error > message "Error: search term did not match precisely one message" > was too vague to explain what happened. > > By appending (matched messages) to the error message it > makes the problem more understandable (e.g when is '0' > user reckons the query had a typo in it). pushed, d