From: "Stefan Monnier" <monnier+gnu/emacs/pretest@RUM.cs.yale.edu>
Cc: ding@gnus.org, GNU Emacs pretest bug list <emacs-pretest-bug@gnu.org>
Subject: Re: article body filling: fill-prefix too long for specified width
Date: Mon, 25 Mar 2002 11:12:28 -0500 [thread overview]
Message-ID: <200203251612.g2PGCSY12966@rum.cs.yale.edu> (raw)
In-Reply-To: <m3g02phnwu.fsf@Janik.cz>
> Hi,
>
> I have received attached e-mail, which can not be displayed in Gnus (from
> CVS) running in current CVS Emacs. The message
>
> fill-prefix too long for specified width
>
> is shown. fill-column is 75 in my setup. Additional details on
> request. I still have this article so I can test your changes.
It must be a bug in my changes in fill.el.
I can't look at it just now, so I'll get back to you later,
Stefan
next prev parent reply other threads:[~2002-03-25 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 17:33 Pavel Janík
2002-03-25 12:57 ` Katsumi Yamaoka
2002-03-25 16:12 ` Stefan Monnier [this message]
2002-03-25 20:38 ` Pavel Janík
2002-03-25 21:52 ` Stefan Monnier
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=200203251612.g2PGCSY12966@rum.cs.yale.edu \
--to=monnier+gnu/emacs/pretest@rum.cs.yale.edu \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.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).