Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@MIT.EDU>
Cc: ding@ifi.uio.no
Subject: Re: Rewriting the subject (Was: [sgnus v0.83] Followup Subject: typos in message.el (patch))
Date: 15 May 1996 00:31:39 -0400	[thread overview]
Message-ID: <ycqybmutv4k.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of (unknown date)


Well the question is, given that i am replying to a message with
Subject: Re[145]: re^4: WORD TOTALLY RO=?ISO-X-666?ABNSAGHS?=OOLZ!!!!!!!!! -reply

Do we really want to construct the new header as:
Subject: Re: Re[145]: re^4: ...

It seems we're only making the problem worse, the header is now even further
from the structure intended by the RFCs.  To some degree i sympathize with
Lars' argument about strengthening the standards, but unless you expect those
packages to actually go away rather than spread it doesn't matter.  I expect
rather than strengthen the standards, we would only make those authors claim,
"well look what happens when people strictly follow the standards; standards
 restrict my ability to support cool new features and make stupid headers like
 these."

And now, what if i write a hook to do my "manual" rewriting of the Subject
automatically, is that ok? What if Lars wrote it? What's the difference?
I don't think you can change the world by making life harder on other
packages, you can make life easier by demonstrating what headers are supposed
to look like.


Greg


  reply	other threads:[~1996-05-15  4:31 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
1996-05-14 18:44                 ` Sudish Joseph
1996-05-15  2:07                   ` Lars Magne Ingebrigtsen
1996-05-15  4:31                     ` Greg Stark [this message]
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=ycqybmutv4k.fsf@fierce-bad-rabbit.MIT.EDU \
    --to=gsstark@mit.edu \
    --cc=ding@ifi.uio.no \
    /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).