From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: message-subject-re
Date: Wed, 29 Aug 2001 14:48:25 -0400 [thread overview]
Message-ID: <m3elpu3do0.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <g088zg2g1fr.fsf@zzz.cisco.com> (Michael.Cook@cisco.com's message of "Wed, 29 Aug 2001 14:34:32 -0400")
Michael.Cook@cisco.com wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> Michael.Cook@cisco.com wrote:
>> > i wanted to inhibit gnus from inserting "Re:" at the beginning of
>>> subject lines. but it seems that that behavior is hard-coded into
>>> message.el. here's a patch to unharden that code.
>>
>> I'd like to see something more general. In particular, I'd like
>> "(was:.*" to be removed from the Subject: in responses. Maybe a hook
>> is in order?
>
> i think you might have misunderstood. message-subject-re is the
> string that gnus inserts into the subject line when you start
> composing a reply (or follow-up).
I understand. I'd like to have a more general facility for modifying
the subject when composing a response. This could incorporate adding
"Re: " and removing a trailing "(was:.*". Maybe also remove
"Re\[[0-9]+\]:" or something.
I see we already have message-header-setup-hook; would this work? But
we don't yet have functions to add to it to clean up the subject. Or
do we?
> the functionality you describe sounds like
> `message-subject-re-regexp'.
I'm not sure what that does - is it used to decide when to add "Re:"?
Or to group threads by subject? Anyway, I don't think it's what I'm
looking for.
paul
next prev parent reply other threads:[~2001-08-29 18:48 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 ` Paul Jarc [this message]
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 ` message-subject-re Paul Jarc
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=m3elpu3do0.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).