Gnus development mailing list
 help / color / mirror / Atom feed
From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: RFC 2646
Date: 11 Oct 1999 13:08:04 +0100	[thread overview]
Message-ID: <uhfjy3xsr.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: Per Abrahamsen's message of "09 Oct 1999 23:19:12 +0200"

Per> Per Abrahamsen <URL:mailto:abraham@dina.kvl.dk>

0> In article <rjhfk0qlkf.fsf@feller.dina.kvl.dk>, Per wrote:

Per> After pGnus is released, I think RFC 2646 support would be a good
Per> thing to work on.  It solves some of the worst shortcommings of
Per> text/plain in a backward compatible way.

That's text/plain;format="flowed", isn't it?  I've thought about this a
little since I saw it appear.  I agree that it would be nice to use the
hint to render such messages; I'm not sure it would be as useful when
generating.  To do it right, you need to set quite a few variables to
ensure that quoting is done exactly as RFC2646 wants (matching ">+ *",
IIRC), and being careful with hard and soft newlines so that some source
code yanked into the message doesn't get wrapped[1].


[1] WIBNI Emacs had a buffer-local variable to say whether newlines were
    hard or soft by defualt in buffers that have use-hard-newlines unset,
    so that killed text can be yanked into buffers with use-hard-newlines
    turned on and the Right Thing would happen.  So C mode would have
    default-newline-property be 'hard, and text mode would have it be
    'soft.



  parent reply	other threads:[~1999-10-11 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-09 21:19 Per Abrahamsen
1999-10-11  8:06 ` Steinar Bang
1999-10-11  8:11   ` Steinar Bang
1999-10-11 13:06     ` Per Abrahamsen
1999-10-12  8:19       ` Steinar Bang
1999-10-11 12:08 ` Toby Speight [this message]
1999-10-11 13:11   ` Per Abrahamsen
1999-11-06 20:54 ` Lars Magne Ingebrigtsen
1999-11-06 21:23   ` Per Abrahamsen
1999-11-07  3:22     ` Lars Magne Ingebrigtsen

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=uhfjy3xsr.fsf@lanber.cam.citrix.com \
    --to=toby.speight@streapadair.freeserve.co.uk \
    /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).