From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Bug tracker breaks rmail-next-same-subject Date: Fri, 12 Dec 2008 18:16:28 -0500 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1229123925 8290 80.91.229.12 (12 Dec 2008 23:18:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Dec 2008 23:18:45 +0000 (UTC) Cc: don@armstrong.com, owner@emacsbugs.donarmstrong.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 13 00:19:49 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LBHIS-0003jz-WD for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2008 00:19:49 +0100 Original-Received: from localhost ([127.0.0.1]:42259 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBHHH-0001vC-1V for ged-emacs-devel@m.gmane.org; Fri, 12 Dec 2008 18:18:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBHFv-0000yS-3z for emacs-devel@gnu.org; Fri, 12 Dec 2008 18:17:11 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBHFs-0000vV-6n for emacs-devel@gnu.org; Fri, 12 Dec 2008 18:17:10 -0500 Original-Received: from [199.232.76.173] (port=38282 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBHFr-0000v6-Tj for emacs-devel@gnu.org; Fri, 12 Dec 2008 18:17:07 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:55451) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LBHFr-0001yT-OF for emacs-devel@gnu.org; Fri, 12 Dec 2008 18:17:07 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1LBHFE-0001bU-9P; Fri, 12 Dec 2008 18:16:28 -0500 In-reply-to: (message from Stefan Monnier on Fri, 12 Dec 2008 14:10:40 -0500) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:106855 Archived-At: > From: Stefan Monnier > Cc: don@armstrong.com, owner@emacsbugs.donarmstrong.com, emacs-devel@gnu.org > Date: Fri, 12 Dec 2008 14:10:40 -0500 > > > The bug tracker modifies the Subject lines, which breaks > > `rmail-next-same-subject' and `rmail-previous-same-subject'. > > > I understand why it tries to do that, but perhaps we can find a better > > way of signalling important status changes without breaking Rmail? > > Could you show some examples, to make sure we talk about the same kinds > of changes? A bug report starts with a Subject such as this: Subject: bug#NNNN: 23.0.60; FOO then it can be modified into this: Subject: Processed: Re: bug#NNNN: 23.0.60; FOO or this: Subject: bug#NNN: marked as done (23.0.60; FOO) or this: Subject: bug#NNNN: Info received (bug#NNNN: 23.0.60; FOO) I'm not sure this is an exhaustive list of all the transformations, it's just what I found in my INBOX this morning, but Don can undoubtedly provide more examples, if they exist. By contrast, rmail-current-subject-regexp allows only for typical reply prefixes, such as "Re:", and arbitrary whitespace changes, such as adding or removing newlines.