Gnus development mailing list
 help / color / mirror / Atom feed
From: Felix Lee <flee@teleport.com>
Subject: Re: Threading
Date: Sat, 18 Apr 1998 19:45:20 -0600	[thread overview]
Message-ID: <199804190247.TAA14582@mail1.teleport.com> (raw)

eesh.  I managed to trace why MH puts a space at the end of
the Subject in replies.

mh repl uses a copy of the subject with the newline
character at the end.  when mh executes a format template,
it smushes out nonprintables, replacing any sequence of them
with a single space.  newline is a nonprintable.  so all
repls will have a space at the end of the subject.

this is mh behavior that looks like it may have been around
forever.  I'm in favor of having gnus compensate for it.

oddly, mh scan doesn't have this extra-space problem,
because scan uses a copy of the subject with trailing space
removed.
--


             reply	other threads:[~1998-04-19  1:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-19  1:45 Felix Lee [this message]
1998-04-24 20:35 ` Threading Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2005-01-28  0:14 threading Sebastian Luque
2005-01-30  0:41 ` threading Johan Bockgård
1998-04-17 20:46 Threading Harry Putnam
1998-04-17 21:39 ` Threading Stephen Zander
1998-04-17 23:17   ` Threading Harry Putnam
1998-04-18  0:58     ` Threading Eze Ogwuma
1998-04-18  1:29       ` Threading Felix Lee
1998-04-18  3:34         ` Threading Harry Putnam
1998-04-18  3:41         ` Threading Eze Ogwuma
1998-04-18  6:27         ` Threading Jason L Tibbitts III
1998-04-18 15:12         ` Threading Justin Sheehy
1998-04-18 20:56           ` Threading Felix Lee
1998-04-19 14:48             ` Threading Justin Sheehy
1998-04-19 21:38               ` Threading Felix Lee
1998-04-19 19:14 ` Threading Dave Love
1998-04-19 22:37 ` Threading Mike McEwan

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=199804190247.TAA14582@mail1.teleport.com \
    --to=flee@teleport.com \
    /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).