From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: message-subject-re
Date: Thu, 30 Aug 2001 00:44:35 -0400 [thread overview]
Message-ID: <m3g0aai2ba.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <g08zo8igvud.fsf@zzz.cisco.com> (Michael.Cook@cisco.com's message of "Wed, 29 Aug 2001 21:50:02 -0400")
Michael.Cook@cisco.com wrote:
> after seeing one too many subject lines that looked like
>
> Subject: Re: Fwd: FW: [list-name] RE: Fwd: foo
>
> it occurred to me that the Re prefix has no real value.
Well, preserving all that without adding another Re: isn't a big
improvement. Maybe it would be best to first strip away all Re:s,
Fwd:s, and such, and then prepend a single Re:. So a response to the
above would get "Re: [list-name] foo".
Yes, the list tag should be preserved in outgoing messages, after the
Re:. Otherwise, when it passes through the list manager, it'll come
out like "[list-name] Re: foo", which breaks everything that expects
to find an existing Re: only at the beginning. Such programs would
then tend to add another Re: at the beginning, which exacerbates the
problem we're trying to ameliorate.
You might hide the tag from yourself when *viewing* messages, but when
responding, it'd be nice to make things come out right for people who
don't hide it. I think doing this might be rather nontrivial, though -
when setting up the response buffer, Gnus would have to re-fetch the
article to find the tag, if any. Or else it'd have to stash the tag
somewhere (a buffer-local variable, maybe?) when removing it.
paul
next prev parent reply other threads:[~2001-08-30 4:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 18:25 message-subject-re Michael.Cook
2001-08-29 18:29 ` message-subject-re Paul Jarc
2001-08-29 18:34 ` message-subject-re Michael.Cook
2001-08-29 18:48 ` message-subject-re Paul Jarc
2001-08-29 19:33 ` message-subject-re Simon Josefsson
2001-08-29 19:40 ` message-subject-re Henrik Enberg
2001-08-29 19:46 ` message-subject-re Paul Jarc
2001-08-29 20:08 ` message-subject-re Michael.Cook
2001-08-29 19:51 ` message-subject-re Frank Schmitt
2001-08-29 20:11 ` message-subject-re Michael.Cook
2001-08-29 23:52 ` message-subject-re Daniel Pittman
2001-08-30 1:50 ` message-subject-re Michael.Cook
2001-08-30 2:31 ` message-subject-re Daniel Pittman
2001-08-30 4:44 ` Paul Jarc [this message]
2001-08-30 16:32 ` message-subject-re Michael.Cook
2001-08-30 16:39 ` message-subject-re Jesper Harder
2001-08-30 13:38 ` message-subject-re Per Abrahamsen
2001-08-29 19:43 ` message-subject-re Paul Jarc
2001-08-29 19:51 ` message-subject-re Simon Josefsson
2001-08-30 14:17 ` message-subject-re Per Abrahamsen
2001-08-31 23:26 ` message-subject-re Simon Josefsson
2001-09-01 14:34 ` message-subject-re Per Abrahamsen
2001-08-30 2:16 ` message-subject-re Steve Youngs
2001-09-05 15:02 ` message-change-subject-interactively (was: message-subject-re) Toby Speight
2001-09-05 15:12 ` message-subject-re Colin Marquardt
2001-09-05 16:10 ` message-subject-re Michael.Cook
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=m3g0aai2ba.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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 NNTP newsgroup(s).