From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: 5.6.16 breaks paragraph-filling
Date: Fri, 26 Jun 1998 20:03:31 GMT [thread overview]
Message-ID: <v1t7m24lylt.fsf@peoria.mt.cs.cmu.edu> (raw)
In-Reply-To: <vxkiulob1gu.fsf@pocari-sweat.jprc.com>
Karl Kleinpaste <karl@jprc.com> writes:
> Gnus v5.6.16; nntp 5.0; nnml 1.0; nnmh 1.0; nndraft 1.0
> XEmacs 20.4 "Emerald" [Lucid] (i386-pc-linux) of Wed Feb 25 1998 on threepwood.idb.hist.no
>
> I am about to revert to .13, because I've just discovered that .16 has
> utterly destroyed paragraph-filling in some manner in *message*
> buffers. M-q is still bound to function fill-paragraph-or-region, but
> it appears that the understanding of paragraph endpoints has been
> utterly lost: The entire message, including the header, is filled as
> though it were one monstrous paragraph.
This appears to be bacause of the filling changes Stallman added. An
extraneous "\\|" got tacked onto the end of paragraph-start in
`message-mode'. Removing that fixed filling for me.
--
Michael Duggan
(md5i@cs.cmu.edu)
.
next prev parent reply other threads:[~1998-06-26 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-26 15:57 Karl Kleinpaste
1998-06-26 20:03 ` Michael Welsh Duggan [this message]
1998-06-26 20:33 ` 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=v1t7m24lylt.fsf@peoria.mt.cs.cmu.edu \
--to=md5i@cs.cmu.edu \
/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).