From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: don@armstrong.com, owner@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: Re: Bug tracker breaks rmail-next-same-subject
Date: Fri, 12 Dec 2008 18:16:28 -0500 [thread overview]
Message-ID: <E1LBHFE-0001bU-9P@fencepost.gnu.org> (raw)
In-Reply-To: <jwvoczhrz0t.fsf-monnier+emacsbugreports@gnu.org> (message from Stefan Monnier on Fri, 12 Dec 2008 14:10:40 -0500)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> 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.
next prev parent reply other threads:[~2008-12-12 23:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 12:44 Bug tracker breaks rmail-next-same-subject Eli Zaretskii
2008-12-12 19:10 ` Stefan Monnier
2008-12-12 23:16 ` Eli Zaretskii [this message]
2008-12-12 21:47 ` Don Armstrong
2008-12-12 23:03 ` Eli Zaretskii
2008-12-12 23:25 ` Don Armstrong
2008-12-12 23:36 ` Eli Zaretskii
2008-12-12 23:57 ` Don Armstrong
2008-12-13 2:41 ` Eli Zaretskii
2008-12-13 9:42 ` Don Armstrong
2008-12-13 22:58 ` Glenn Morris
2008-12-13 23:14 ` Bugs against emacsbugs.donarmstrong.com Don Armstrong
2008-12-13 23:33 ` Glenn Morris
2008-12-14 0:23 ` Don Armstrong
2008-12-14 3:51 ` Stefan Monnier
2008-12-14 8:06 ` Stephen J. Turnbull
2008-12-14 10:13 ` Don Armstrong
2008-12-14 20:53 ` Glenn Morris
2008-12-14 21:27 ` Stefan Monnier
2008-12-17 5:39 ` Don Armstrong
2008-12-17 16:10 ` Stefan Monnier
2008-12-18 7:43 ` Don Armstrong
2008-12-18 21:46 ` Stefan Monnier
2008-12-14 8:14 ` Stephen J. Turnbull
2008-12-14 2:50 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LBHFE-0001bU-9P@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=don@armstrong.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=owner@emacsbugs.donarmstrong.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.