Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Cc: Greg Troxel <gdt@work.lexort.com>
Subject: Re: plain text, Ipod, format=flowed always
Date: Mon, 14 Jan 2013 12:32:03 +0100	[thread overview]
Message-ID: <87sj64vw3w.fsf@gilgamesch.quim.ucm.es> (raw)
In-Reply-To: <smulic3w7r4.fsf@linuxpal.mit.edu>

>> "Greg" == Greg Troxel <gdt@work.lexort.com> writes:

   > Uwe Brauer <oub@mat.ucm.es> writes:

   >> See also:  http://www.emacswiki.org/emacs/GnusFormatFlowed

   > I find this wiki page hard to follow:

   >   The take on 'older' vs 'graphical' seems to lack the proper standards
   >   perspective (and probably should mention the non-compliant non-flowed
   >   issue).

   >   The "physical" vs "logical" line is an odd way to put it;
   >   format=flowed is about giving the receiving MUA permission to reflow
   >   paragraphs, while still sending mail that complies with line length
   >   norms.


I have played around with this for the last days.

    -  if you just send a mail with use-hard-newlines, with or without using
       newlines preceding a paragraph-start line, then everything is
       _fine_ and behaves as expected, I can read that mail say on my
       Ipod just nicely since format=flowed is on.

    -  However, if I *reply* to an email, then this are much more
       complicated, because with use-hard-newlines, I see stuff like


> this blablak text > more text

       so the "best" solution would be to unfill the whole message
       (beyond 70 char) but I don't like this solution neither.


Uwe Brauer 




  reply	other threads:[~2013-01-14 11:32 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
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 [this message]
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=87sj64vw3w.fsf@gilgamesch.quim.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.org \
    --cc=gdt@work.lexort.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).