From: Uwe Brauer <oub@mat.ucm.es>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, ding@gnus.org
Subject: Re: plain text, Ipod, format=flowed always
Date: Tue, 01 Jan 2013 18:18:37 +0100 [thread overview]
Message-ID: <87k3rwu8ia.fsf@mat.ucm.es> (raw)
In-Reply-To: <m34nj2p7ao.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 31 Dec 2012 16:31:27 +0100")
>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> Yes, very lines! :-) Let's see. I've now set
>> `use-hard-newlines'
>> here, and then things should (according to the
>> documentation) turn
>> into format=flowed. But will it?
>
Content-Type: text/plain; format=flowed
> It diddly doo did it.
Hm I used use-hard-newlines for this message, indeed
Content-Type: text/plain; format=flowed
Is added *but* also a lot of (unwanted) newlines, at least
for me my
message looks different from the one you sent me. Either
use-hard-newlines behaves differently in Xemacs or I have
some
additional setting in my gnus-init file
.
Uwe
next prev parent reply other threads:[~2013-01-01 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 10:05 Uwe Brauer
2012-12-24 20:09 ` Lars Ingebrigtsen
2012-12-28 13:52 ` Uwe Brauer
2012-12-31 15:28 ` Lars Magne Ingebrigtsen
2012-12-31 15:31 ` Lars Magne Ingebrigtsen
2013-01-01 17:18 ` Uwe Brauer [this message]
2013-01-01 20:00 ` Lars Magne Ingebrigtsen
2013-01-01 21:45 ` Uwe Brauer
2013-01-01 22:22 ` Elias Oltmanns
2013-01-02 5:02 ` Lars Magne Ingebrigtsen
2013-01-02 5:05 ` Lars Magne Ingebrigtsen
2013-01-08 11:21 ` Uwe Brauer
2013-01-08 23:54 ` Greg Troxel
2013-01-14 11:32 ` Uwe Brauer
2013-01-14 14:23 ` [SOLVED] (was: plain text, Ipod, format=flowed always) Uwe Brauer
2013-01-08 12:17 ` use-hard-newlines bizarre " Uwe Brauer
2013-01-10 18:16 ` Make newlines between paragraphs hard???? " Uwe Brauer
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=87k3rwu8ia.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
--cc=larsi@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).