From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 2856D431FD0 for ; Mon, 11 Jul 2011 14:05:47 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4v44z8EdA6hA for ; Mon, 11 Jul 2011 14:05:45 -0700 (PDT) Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by olra.theworths.org (Postfix) with ESMTP id 7A8DA431FB6 for ; Mon, 11 Jul 2011 14:05:45 -0700 (PDT) X-AuditID: 1209190e-b7c39ae000000a8c-e2-4e1b65798714 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 19.D7.02700.9756B1E4; Mon, 11 Jul 2011 17:04:57 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id p6BL5i06013234; Mon, 11 Jul 2011 17:05:44 -0400 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p6BL5gBx007694 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 11 Jul 2011 17:05:44 -0400 (EDT) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.72) (envelope-from ) id 1QgNfY-0003Ar-8U; Mon, 11 Jul 2011 17:05:32 -0400 Date: Mon, 11 Jul 2011 17:05:32 -0400 From: Austin Clements To: Pieter Praet Subject: Re: [PATCH v2] emacs: bad regexp @ `notmuch-search-process-filter' Message-ID: <20110711210532.GC25558@mit.edu> References: <20110705214234.GA15360@mit.edu> <1310416993-31031-1-git-send-email-pieter@praet.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1310416993-31031-1-git-send-email-pieter@praet.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IRYrdT0a1MlfYzuLvE2OL6zZnMFr9f32B2 YPJ4tuoWs0fHvsusAUxRXDYpqTmZZalF+nYJXBln35oW7OGo2PjvKGMD4yO2LkZODgkBE4nF Xa3MELaYxIV764HiXBxCAvsYJY497mWCcDYwSixbdpIFwjnJJHFwwWpGCGcJo0TP08/sIP0s AqoSW05cBrPZBDQktu1fzghiiwgoS5x+8hMsziygJbF14wewuLCAt0TfirNgNq+AjsSViQ9Z QWwhgWSJVfcPsELEBSVOznzCAtN7499LoJM4gGxpieX/OEDCnAKOEm2bloK9ICqgInFtfzvb BEahWUi6ZyHpnoXQvYCReRWjbEpulW5uYmZOcWqybnFyYl5eapGusV5uZoleakrpJkZQWHNK 8u1g/HpQ6RCjAAejEg/vKmlpPyHWxLLiytxDjJIcTEqivA0pQCG+pPyUyozE4oz4otKc1OJD jBIczEoivLvZgXK8KYmVValF+TApaQ4WJXHeKO//vkIC6YklqdmpqQWpRTBZGQ4OJQleFmD8 CgkWpaanVqRl5pQgpJk4OEGG8wAN/wKymLe4IDG3ODMdIn+KUVFKnPchSEIAJJFRmgfXC0s7 rxjFgV4R5j0JUsUDTFlw3a+ABjMBDX4tLQkyuCQRISXVwGjD1HRMLsovueex6v3ZE4+5rH1u U9CnHtgyc/1NoaPrHkbr7dzmOqd28bHFxxc7zr+1laHmzSnrM0+Lr7QUfwkRbsjhurF+TVIM /5+9y3Tclc2qpTaoXTzg3mj7Z4Uc42kmxvStModro/cuYthQLzSb5dObbU0XTrp0ND9dtKdP 9JT6uZV2my8qsRRnJBpqMRcVJwIAU76f5BYDAAA= Cc: Notmuch Mail X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Mon, 11 Jul 2011 21:05:47 -0000 Quoth Pieter Praet on Jul 11 at 10:43 pm: > TL;DR: I can haz regex pl0x? Oof, what a pain. I'm happy to change the output format of search; I hadn't realized how difficult it would be to parse. In fact, I'm not sure it's even parsable by regexp, because the message ID's themselves could contain parens. So what would be a good format? One possibility would be to NULL-delimit the query part; as distasteful as I find that, this part of the search output isn't meant for user consumption. Though I fear this is endemic to the dual role the search output currently plays as both user and computer readable. I've also got the code to do everything using document ID's instead of message ID's. As a side-effect, it makes the search output clean and readily parsable since document ID's are just numbers. Hence, there are no quoting or escaping issues (plus the output is much more compact). I haven't sent this to the list yet because I haven't had a chance to benchmark it and determine if the performance benefits make exposing document ID's worthwhile.