Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: WARNING: The attached message make Gnus eat all resources
Date: Fri, 26 Jul 2002 14:53:01 +0200	[thread overview]
Message-ID: <iluvg72r6qa.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3ptxe8pjr.fsf@fermat.mts.jhu.edu> (Nevin Kapur's message of "Tue, 23 Jul 2002 10:58:53 -0400")

Nevin Kapur <nevin@jhu.edu> writes:

> The attached message will make Gnus eat all resources for a *long*
> time -- I C-g'd after about a minute.  Debug on quit suggests
> something to do with flow-fill and filladapt in turn.
>
> On an unrelated note, when I tried to forward the message with C-c
> C-f, it stripped out the Content-Type header which made the bug go
> away.

Does this fix it?

Fill-adapt is IMHO evil as it redefines existing elisp functions.

--- flow-fill.el.~6.11.~	2002-06-09 21:47:48.000000000 +0200
+++ flow-fill.el	2002-07-08 15:30:31.000000000 +0200
@@ -135,7 +135,8 @@
 	  (unless sig
 	    (condition-case nil
 		(let ((fill-prefix (when quote (concat quote " ")))
-		      (fill-column (eval fill-flowed-display-column)))
+		      (fill-column (eval fill-flowed-display-column))
+		      filladapt-mode)
 		  (fill-region (fill-flowed-point-at-bol)
 			       (min (1+ (fill-flowed-point-at-eol)) (point-max))
 			       'left 'nosqueeze))




  parent reply	other threads:[~2002-07-26 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 14:58 Nevin Kapur
2002-07-23 17:57 ` Reiner Steib
2002-07-23 18:10   ` Josh Huber
2002-07-23 20:11     ` Harry Putnam
2002-07-24  7:40 ` Niklas Morberg
2002-07-26 12:53 ` Simon Josefsson [this message]
2002-07-26 15:40   ` Nevin Kapur
2002-07-26 16:39     ` Simon Josefsson
2002-07-28 14:47       ` Nevin Kapur
2002-12-30 17:19       ` Lars Magne Ingebrigtsen
2002-12-30 17:17 ` 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=iluvg72r6qa.fsf@latte.josefsson.org \
    --to=jas@extundo.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).