Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch))
Date: 14 May 1996 13:28:04 -0400	[thread overview]
Message-ID: <x7pw875fmj.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: Per Abrahamsen's message of 14 May 1996 17:25:07 +0200

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:

RP> Or a pretty good reason to massage it into something that a human
RP> can more easilly parse.
PA> Well, that is what nn tried to do with Re^4: and Lotus try to do
PA> with the "- Reply" string.

Just because something has been done poorly is not reason to not do it
right somewhere else.

PA> I'd say massage the subject as much as you want for presentation
PA> purposes in the article and subject buffers, but when you generate a
PA> reply or followup, make the default subject line be in strict
PA> compliance with The Seal and with Son-of-RFC1036.

You need to be careful, here.  For example, is scoring/killing done on
the real header contents, or on the massaged version?  And if the
former, how to make that apparant in the crossover?  But otherwise this
is quite workable; I am all for it.  In fact, much of the code to do
this already exists in gnus-simplify-subject-fuzzy and the -regexp
variable.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQCVAwUBMZjCpp6VRH7BJMxHAQEdOgQArBL05NJ8rqnxBCJr0xFe9qWwgRexbdKI
uDblRNdUs58yHl0xdWLYCKLzmnIQxaIdbkoNouhE2APLpKSLn4QuSUnET7qtGyRo
Y1GbK9PVCwgaecHx1zzBCwjdoJ1LbDQ5vFKZDdhJijnf7M9ZTFDQr7ivtJZjETfu
Uwan18Yt1VM=
=R8wj
-----END PGP SIGNATURE-----
-- 
Richard Pieri/Information Services \ If you're not receiving enough attention,
<ratinox@unilab.dfci.harvard.edu>   \ try knocking over some very expensive
http://www.dfci.harvard.edu/         \ antique lamps. -A cat's guide to life


  reply	other threads:[~1996-05-14 17:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-09 18:21 [sgnus v0.83] Followup Subject: typos in message.el (patch) Steven L Baur
1996-05-09 21:58 ` Lars Magne Ingebrigtsen
1996-05-10  1:50   ` Raja R Harinath
1996-05-10  3:29     ` Steven L Baur
1996-05-11  0:37       ` Lars Magne Ingebrigtsen
1996-05-14  4:41         ` Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch)) Jason L Tibbitts III
1996-05-14 12:25           ` Per Abrahamsen
1996-05-14 14:32             ` Richard Pieri
1996-05-14 15:25               ` Per Abrahamsen
1996-05-14 17:28                 ` Richard Pieri [this message]
1996-05-14 18:44                 ` Sudish Joseph
1996-05-15  2:07                   ` Lars Magne Ingebrigtsen
1996-05-15  4:31                     ` Greg Stark
1996-05-15 14:10                       ` Sudish Joseph
1996-05-15 21:53                         ` Edward J. Sabol
1996-05-15 22:25                     ` Steven L Baur
1996-05-15  3:15                   ` Greg Stark

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=x7pw875fmj.fsf@unilab.dfci.harvard.edu \
    --to=ratinox@unilab.dfci.harvard.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).