From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] view: case-insensitive "Re:" check for replies
Date: Sun, 23 Aug 2015 22:35:44 +0000 [thread overview]
Message-ID: <1440369345-13435-2-git-send-email-e@80x24.org> (raw)
This is to match what Mail::Thread nad our own search
relies on. However, we will be more lenient on spaces,
though.
---
lib/PublicInbox/View.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index f9081a6..72bbb94 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -419,7 +419,7 @@ sub html_footer {
Email::Address->purge_cache if $standalone;
my $subj = $mime->header('Subject') || '';
- $subj = "Re: $subj" unless $subj =~ /\bRe:/;
+ $subj = "Re: $subj" unless $subj =~ /\bRe:/i;
my $mid = $mime->header('Message-ID');
my $irt = uri_escape_utf8($mid);
delete $cc{$to};
--
EW
reply other threads:[~2015-08-23 22:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440369345-13435-2-git-send-email-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).