From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Problem with filling and hard newlines in message-mode
Date: Sat, 11 Sep 2010 01:34:48 +0200 [thread overview]
Message-ID: <m3pqwl5g13.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87tyly1z6g.fsf@keller.adm.naquadah.org>
Julien Danjou <julien@danjou.info> writes:
> It seems that if the buffer has hard newlines, the mail is encoded using
> format=flowed. And that make my message totally weird. This seems to be
> old and I never heard about this `flowed' stuff.
>
> Does it ring a bell? I can sent such a message to the list if needed.
Yes, format=flowed is old, well-known stuff.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2010-09-10 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 10:28 Julien Danjou
2010-09-06 20:16 ` Lars Magne Ingebrigtsen
2010-09-07 7:32 ` Julien Danjou
2010-09-07 16:21 ` Lars Magne Ingebrigtsen
2010-09-09 19:42 ` Julien Danjou
2010-09-10 23:34 ` Lars Magne Ingebrigtsen [this message]
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=m3pqwl5g13.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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).