Gnus development mailing list
 help / color / mirror / Atom feed
From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: ">" -vs- "Re:" -- is this guy crazy?
Date: 25 Feb 1998 14:34:18 -0500	[thread overview]
Message-ID: <glmpvkbwkat.fsf@caffeine.rcf.mitre.org> (raw)
In-Reply-To: SL Baur's message of "24 Feb 1998 14:02:58 -0800"

SL Baur <steve@xemacs.org> writes:

> No.  I've never seen it.  There is a (broken) Microsoft mailer that
> uses `FW: '.  There is a (broken) Novell mailer that appends a
> `-Reply'.  There are various (broken) Unix mailers that use `Re[2]: '
> `Re[3]: ', etc.  VM doesn't add anything by default.
> 
> The only acceptable thing to do is to prepend a `Re: ' if one is not
> already there, otherwise don't add anything.

I notice that you nicely avoid directly saying that VM is broken in
this regard, even though it is obvious from the second sentence above
that you agree that it is.  Correct me if I've misread.

I'll come out and say it: this behavior of VM is broken.

> > It breaks Gnus threading (as readers of the ntemacs list will have
> > noticed).
> 
> It shouldn't if the References: header is properly formed.

Lots of mail clients don't create a References: header, or create bad
ones.

One of my current pet peeves: the way that mh breaks threading.

If you reply/followup to a message, it does the right thing with Re:
but then appends a space to the Subject: as well.  

I know that Gnus can be customized to ignore the space, but that does
not change that it is broken behavior on mh's part.

I had hoped that this would be fixed in nmh, but I have seen similarly
broken messages coming from nmh users.

Feh.

> Since when has Gnus been customizable in this area?

See the variables gnus-simplify-*

-- 
Justin Sheehy

In a cloud bones of steel.
  




  parent reply	other threads:[~1998-02-25 19:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-24 21:41 Matt Armstrong
1998-02-24 21:54 ` Karl Kleinpaste
1998-02-24 21:56 ` Wes Hardaker
1998-02-24 22:02 ` SL Baur
1998-02-24 23:14   ` Matt Armstrong
1998-02-25 10:22     ` Per Abrahamsen
1998-02-25 20:30     ` Dave Love
1998-02-26 10:38       ` Per Abrahamsen
1998-02-27 19:03         ` in-reply-to: threading [was Re: ">" -vs- "Re:" -- is this guy crazy?] Dave Love
1998-02-28  5:54           ` Lars Magne Ingebrigtsen
1998-03-02 12:08             ` Per Abrahamsen
1998-03-04 11:41               ` Dave Love
1998-02-26 20:58       ` ">" -vs- "Re:" -- is this guy crazy? Ken Raeburn
1998-02-24 23:38   ` lantz moore
1998-02-25  0:45   ` Christian Nybø
1998-02-25  7:46     ` ">" -vs- " jari.aalto
1998-02-25  8:41     ` ">" -vs- "Re:" " Steinar Bang
1998-02-25 19:34   ` Justin Sheehy [this message]
1998-02-25 22:18     ` Steinar Bang
1998-02-26  2:15       ` Justin Sheehy
1998-02-26  8:08         ` Steinar Bang
1998-02-26  8:16       ` Richard Coleman
1998-02-27  4:39         ` Jason R Mastaler
1998-03-02 17:11           ` David S. Goldberg
1998-02-25 22:35     ` SL Baur
1998-02-25 22:40       ` Lars Balker Rasmussen
1998-02-26  3:46   ` Aaron M. Ucko
1998-02-26  8:04     ` Steinar Bang

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=glmpvkbwkat.fsf@caffeine.rcf.mitre.org \
    --to=justin@linus.mitre.org \
    /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).