Gnus development mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
Subject: Re: controlling whether gnus splits long Subject: lines, for example, this one
Date: Wed, 07 Nov 2001 10:48:42 +0100	[thread overview]
Message-ID: <87d72uj4hx.fsf@pixie.eng.ascend.com> (raw)
In-Reply-To: <y9ljsehe.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Tue, 06 Nov 2001 23:48:13 +0100")

Frank Schmitt <usereplyto@Frank-Schmitt.net> wrote:
> Jim Meyering <jim@meyering.net> writes:
>>Can any of you tell me how to convince Gnus (or whatever is
>>doing it) not to split long Subject lines in my outgoing messages?
>>
>>For example, when I look at my Gcc'd copy of this message,
>>I'll find that Gnus has inserted a newline into the above Subject line.
>
> Why do you want to do this? Long headers have to be splited since there
> is a maximum line length for header lines.

Are you sure they absolutely *must* be split?
Just because a standard says it must be done doesn't make it right --
though going against the standard can be painful :-)

My particular problem is in corresponding with people whose mail clients
put the split line back together in such a way that they end up removing
a space that (in the original subject) used to separate two words.

Here's an example:
Yesterday I sent a message with a subject like this:

  Subject: ............................................ remaining files associated ...

a colleague replied with this:

  Subject: ............................................ remaining filesassociated ...

to which I replied, and he replied again, with this:

  Subject: ............................................ remainingfilesassociated  ...

I don't like seeing my Subject: lines mangled like that.
It makes it much harder to find things in the archive later.
BTW, the mail client that pasted the lines together without
the intervening space appears to be Mozilla 4.73.



  parent reply	other threads:[~2001-11-07  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 22:15 Jim Meyering
2001-11-06 22:48 ` Frank Schmitt
2001-11-07  6:40   ` Matt Armstrong
2001-11-07  9:13     ` Peter Makholm
2001-11-07 16:11       ` Matt Armstrong
2001-11-07  9:48   ` Jim Meyering [this message]
2001-11-07 10:03     ` Didier Verna

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=87d72uj4hx.fsf@pixie.eng.ascend.com \
    --to=jim@meyering.net \
    /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).