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 9C91D431FAF for ; Wed, 18 Jan 2012 11:11:22 -0800 (PST) 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 Gqr7P2XNlvDm for ; Wed, 18 Jan 2012 11:11:22 -0800 (PST) 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 25E31431FAE for ; Wed, 18 Jan 2012 11:11:22 -0800 (PST) X-AuditID: 1209190e-b7f7c6d0000008c3-f3-4f1719597f1f Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 17.B4.02243.959171F4; Wed, 18 Jan 2012 14:11:21 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id q0IJBKqL011295; Wed, 18 Jan 2012 14:11:21 -0500 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 q0IJBJea013991 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 18 Jan 2012 14:11:20 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1RnauX-0001ZM-Gx; Wed, 18 Jan 2012 14:11:05 -0500 Date: Wed, 18 Jan 2012 14:11:05 -0500 From: Austin Clements To: David Bremner Subject: Re: RFC: tag macros Message-ID: <20120118191105.GE16740@mit.edu> References: <874nvtvzm5.fsf@convex-new.cs.unb.ca> <20120118183304.GC16740@mit.edu> <87wr8o7rzb.fsf@rocinante.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87wr8o7rzb.fsf@rocinante.cs.unb.ca> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgleLIzCtJLcpLzFFi42IR4hRV1o2UFPc3+PlV1+JGazejxfWbM5kd mDyerbrF7LHl0HvmAKYoLpuU1JzMstQifbsEroyunSUFB9krZh24wdjA+Jm1i5GTQ0LARGJS /1lmCFtM4sK99WwgtpDAPkaJvxeDuxi5gOwNjBJf/9+CSpxkkvh0WhsisYRR4u2f5UDdHBws AqoSW09Jg9SwCWhIbNu/nBHEFgEKX902GayXWUBLYuvGD2BxYQEZid7D68BsXgEdia8r5zND zK+WWHVuFTtEXFDi5MwnLDC9N/69ZAJZxSwgLbH8HwdImFPAUOLDgqlgv4gKqEhMObmNbQKj 0Cwk3bOQdM9C6F7AyLyKUTYlt0o3NzEzpzg1Wbc4OTEvL7VI11gvN7NELzWldBMjOKAl+XYw fj2odIhRgINRiYc3QkTcX4g1say4MvcQoyQHk5Ior4c4UIgvKT+lMiOxOCO+qDQntfgQowQH s5II7xc+oBxvSmJlVWpRPkxKmoNFSZxXTeudn5BAemJJanZqakFqEUxWhoNDSYL3lwRQo2BR anpqRVpmTglCmomDE2Q4D9Dw8yA1vMUFibnFmekQ+VOMilLivK9AEgIgiYzSPLheWMJ5xSgO 9Iow732QKh5gsoLrfgU0mAlosEeTGMjgkkSElFQDo1fo00P267e5qcvN6ty3+8Cnxp9Jdv/r D7lOL/o7679cwQOzCm8bl9CG+bcVH0+7ULzo5PQjDL+ip69fOas4wufgUWFlK/H0x+943lov ud01Y+8rZecgmdfrb4vZKs3I55otkZL2+ZnEtsUvZwQf3Vyj+NSWyTfqwZVQc08VH7Osq479 bc7dEkosxRmJhlrMRcWJADaXp4ITAwAA 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: Wed, 18 Jan 2012 19:11:22 -0000 Quoth David Bremner on Jan 18 at 3:03 pm: > On Wed, 18 Jan 2012 13:33:04 -0500, Austin Clements wrote: > > Quoth David Bremner on Jan 18 at 10:45 am: > > > What about simply providing an API that takes a bunch of tag > > operations and applies them to the current thread/message/region? > > My main motivation here is (as you can probably see from the example) > dealing with patches, and in that setting, tagging the whole thread is > is almost never what you want. > > That aside, thread tagging is already there in search view, and I guess > could be done by selecting the whole thread and tagging that region. > > I haven't really looked at how to apply tags to regions in > notmuch-show-mode. Is there code around that does that? Or more > generally iterate over messages in a region? Sorry, that was all a bit of a red herring in my email. The high-level point I was trying to make is really what Jamie said.