From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: mm-* "format=flowed" error
Date: 25 May 2000 18:50:40 +0200 [thread overview]
Message-ID: <iluvh02d15r.fsf@xiphias.pdc.kth.se> (raw)
In-Reply-To: Karl Kleinpaste's message of "25 May 2000 11:55:45 -0400"
Karl Kleinpaste <karl@charcoal.com> writes:
> The message attached below induces an end-of-buffer error & a stack trace.
>
> Signaling: (end-of-buffer)
> fill-region-as-paragraph(972 1099 left nosqueeze)
> fill-region(972 1099 left nosqueeze)
> fill-flowed()
I'm not able to reproduce it with any emacs I have available, could
you perhaps edebug-defun `fill-flowed' and cut'n'paste the content of
the buffer `fill-flowed' works in into a new buffer, and see whether
you can get `fill-flowed' to give the same backtrace when you invoke
it manually? (phew) If so, please mail me the buffer content.
Do you get the backtrace if you click on the rfc822 attachment in your
post to the ding list? (To make sure it wasn't distorted along the
way.)
next prev parent reply other threads:[~2000-05-25 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-25 15:55 Karl Kleinpaste
2000-05-25 16:50 ` Simon Josefsson [this message]
2000-05-25 19:59 ` Karl Kleinpaste
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=iluvh02d15r.fsf@xiphias.pdc.kth.se \
--to=jas@pdc.kth.se \
--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).