Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: Re: New default change: Automatic article filling
Date: Sun, 31 Oct 2010 17:52:38 -0400	[thread overview]
Message-ID: <smu62wirpw9.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <m3r5f6giyn.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 31 Oct 2010 22:17:52 +0100")

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]


  Anybody have a good heuristic for seeing whether a paragraph is code?

Perhaps make this conditional on sending MUA.  The problem seems to be
broken support for format=flowed, and confusion between an auto-filling
UI (which is fine) and proper encoding of a message from such a UI
(which seems rare).

As a data point, Apple's Mail.app is broken.


[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2010-10-31 21:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 21:17 Lars Magne Ingebrigtsen
2010-10-31 21:28 ` Russ Allbery
2010-10-31 21:34   ` Lars Magne Ingebrigtsen
2010-10-31 21:52     ` Lars Magne Ingebrigtsen
2010-10-31 21:52 ` Greg Troxel [this message]
2010-11-02  0:29 ` Katsumi Yamaoka
2010-11-02  2:20   ` Katsumi Yamaoka
2010-11-02 19:42     ` Lars Magne Ingebrigtsen
2010-11-02 19:42   ` Lars Magne Ingebrigtsen
2010-11-06 18:36 ` Ralf Angeli
2010-11-07 18:07   ` Greg Troxel
2010-11-08 19:54   ` Lars Magne Ingebrigtsen
2010-11-08 20:16     ` Ralf Angeli
2010-11-08 21:32       ` Lars Magne Ingebrigtsen
2010-11-07 23:06 ` Ludovic Courtès
2010-11-25  9:05   ` Ludovic Courtès
2010-11-26  1:17     ` Lars Magne Ingebrigtsen
2010-11-26 10:01       ` Steinar Bang
2010-11-28 10:34         ` Lars Magne Ingebrigtsen
2010-11-28 11:14           ` Rupert Swarbrick

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=smu62wirpw9.fsf@linuxpal.mit.edu \
    --to=gdt@work.lexort.com \
    --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).