Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: New default change: Automatic article filling
Date: Sun, 31 Oct 2010 22:17:52 +0100	[thread overview]
Message-ID: <m3r5f6giyn.fsf@quimbies.gnus.org> (raw)

gnus-treat-fill-long-lines now defaults to '(typep "text/plain"), and
this now points to `gnus-article-fill-cited-long-lines' instead of the
simpler version.  So Gnus will do article filling based on citation
parsing if the lines are wider than the frame width.

There are probably some issues with this here and there, so let me know
whether it's too annoying.  I've looked through about a 100 messages
from "real people" (i.e., just the kind of people that doesn't wrap
their lines when sending), and it looks much better to me than before.
But it may do totally the wrong thing with code.

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

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 21:17 Lars Magne Ingebrigtsen [this message]
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
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=m3r5f6giyn.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).