From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: fill bug still there [Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop]
Date: 29 May 2001 19:22:20 +0200 [thread overview]
Message-ID: <vafy9rgax4j.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <yz1d78t1ixo.fsf@milhouse.cs.cornell.edu> (Paul Stodghill's message of "28 May 2001 13:45:10 -0400")
On 28 May 2001, Paul Stodghill wrote:
>> looking-at("--text follows this line--$\\|[ ]*$\\|--
>> $\\|---+$\\|^?$\\|.*wro
>> te:$\\|\\(\\([ ]*\\(\\w\\|[-_.]\\)+>+\\|[ ]*[]>>|:}+]\\)+\\)[ ]*$")
>> # bind (quoted point beg end leading-space bolp not-break arg)
>> message-newline-and-reformat(nil t)
>> # bind (arg)
>> message-fill-paragraph(nil)
>> # bind (function fill-paragraph-function arg)
>> #<compiled-function (arg) "...(54)" [function before end start arg fill-paragr
>> aph-function nil forward-paragraph newline 1 backward-paragraph fill-region fill
>> -region-as-paragraph use-hard-newlines] 5 1025528 (list (if current-prefix-arg .
>> ..))>(nil)
>> apply(#<compiled-function (arg) "...(54)" [function before end start arg fill-
>> paragraph-function nil forward-paragraph newline 1 backward-paragraph fill-regio
>> n fill-region-as-paragraph use-hard-newlines] 5 1025528 (list (if current-prefix
>> -arg ...))> nil)
>> # bind (args function)
>> filladapt-funcall(fill-paragraph nil)
It seems that the lockup is caused by filladapt. Does it go away when
you disable filladapt? Or is filladapt always enabled in XEmacs?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-05-29 17:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 13:50 XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Paul Stodghill
2001-05-21 14:09 ` Hrvoje Niksic
2001-05-21 14:37 ` Josh Huber
2001-05-21 15:05 ` Olivier Fambon
2001-05-21 15:15 ` Paul Stodghill
2001-05-21 16:07 ` Andy Piper
2001-05-21 19:13 ` Paul Stodghill
2001-05-21 19:14 ` Paul Stodghill
2001-05-28 17:45 ` fill bug still there [Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop] Paul Stodghill
2001-05-29 17:20 ` Simon Josefsson
2001-05-29 17:24 ` Paul Stodghill
2001-05-29 17:22 ` Kai Großjohann [this message]
2001-05-29 17:26 ` Paul Stodghill
2001-05-29 17:50 ` Kai Großjohann
2001-05-29 17:56 ` Paul Stodghill
2001-05-27 3:38 ` critical quit Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Ben Wing
2001-05-28 17:44 ` Paul Stodghill
2001-05-30 1:28 ` Ben Wing
2001-05-30 7:08 ` Wow Ken McGlothlen
2001-05-30 9:26 ` Wow Kai Großjohann
2001-05-30 21:19 ` Wow Ken McGlothlen
2001-05-30 21:26 ` Wow Kai Großjohann
2001-05-31 9:10 ` Wow Steinar Bang
2001-06-01 21:30 ` Wow Ken McGlothlen
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=vafy9rgax4j.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).