Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Integrating message-utils.el into Gnus?
Date: Wed, 13 Feb 2002 20:04:25 -0500	[thread overview]
Message-ID: <2ng044oova.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <v9wuxgzzko.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 14 Feb 2002 01:17:43 +0100")

Reiner Steib <4uce.02.r.steib@gmx.net> writes:

> On Fri, Apr 27 2001, Matthias Wiehl wrote:
>
> [Full quote, because cited message is quite old]
>
>> At <http://www.coling.uni-freiburg.de/~schauer/emacs.html>, Holger
>> Schauer [1] provides a file called message-utils.el [2].  It contains
>> a few complementary functions for use with Gnus' message-mode.
>>
>> Personally, I find three of those functions extraordinarily useful:
>>
>>   o  `message-change-subject' asks for a new subject, and modifies the
>>      message's Subject header in a way that is RFC 1036bis compliant:
>>      `new subject (was: old subject)'.
>>
>>   o  `message-strip-subject-was' can be hooked into
>>      `message-header-setup-hook'.  It strips `(was: old subject)' from
>>      the Subject header (which is what user agents are supposed to do)
>>      as far as I know) when entering message-mode.  Both slrn and tin
>>      do this out-of-the-box.
>>
>>   o  `message-xpost-fup2' asks for a newsgroup name (providing
>>      tab-completion via gnus-newsrc-alist).  This name is then
>>      appended to the Newsgroups header, and the Followup-To header
>>      is modified to contain only the given newsgroup name as its
>>      value.  Furthermore, a customizable note is inserted in the
>>      message body, saying that a Followup-To header has been set.
>>
>> Is there any chance of integrating these functions into the standard
>> Gnus distribution?
>>
>> -------
>> [1] <mailto:Holger.Schauer@gmx.de>
>> [2] <http://www.coling.uni-freiburg.de/~schauer/resources/emacs/message-utils.el.gz>
>
> `message-change-subject' and `message-strip-subject-was' are features
> that are requested quite often (and the usual answer is `Gnus +
> message-utils.el'). WIBNI Gnus would support this out of the box?

If Holger agrees to sign the FSF assignment, I can integrate it into
the future Gnus distribution.  I've sent him the request form.

ShengHuo



      reply	other threads:[~2002-02-14  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27 20:48 Matthias Wiehl
2001-04-28  1:34 ` Toby Speight
2002-02-14  0:17 ` Reiner Steib
2002-02-14  1:04   ` ShengHuo ZHU [this message]

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=2ng044oova.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.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).