From: Colin Marquardt <colin.marquardt@usa.alcatel.com>
Subject: Re: Flowed format
Date: 25 Jan 2001 12:37:25 -0800 [thread overview]
Message-ID: <ysd6itn3cqre.fsf@sol-cmarquar.pet.usa.alcatel.com> (raw)
In-Reply-To: <m3snm7fkhs.fsf@reader.newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> I get these horribly formatted messages from the tech staff at my ISP.
[...]
> What I see are usually a greeting line then maybe 5-6 empty lines,
> then another line or two with another major gap then a message in what
> looks like a long continuous line.
[...]
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Not sure about the effects multipart might have, but is your fill-column
variable set to sensible values for that buffer? Was a problem for me
once...
Colin
next prev parent reply other threads:[~2001-01-25 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 20:24 Harry Putnam
2001-01-25 20:37 ` Colin Marquardt [this message]
2001-01-25 21:50 ` Harry Putnam
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=ysd6itn3cqre.fsf@sol-cmarquar.pet.usa.alcatel.com \
--to=colin.marquardt@usa.alcatel.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).