From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: preparing Gnus info manuals "freezes" Emacs-20.2
Date: 23 Feb 1998 05:27:50 +0100 [thread overview]
Message-ID: <m3u39rrlmh.fsf@sparky.gnus.org> (raw)
In-Reply-To: Richard Hoskins's message of "22 Feb 1998 22:14:31 -0500"
Richard Hoskins <rmh@interlaced.net> writes:
> Emacs will hang when formatting (not always in the same place), and
> when I quit with C-g, I am left with a `gnus' buffer with hundreds of
> thousands of blank lines.
[...]
> Signaling: (quit)
> current-left-margin()
> indent-to-left-margin()
> fill-region-as-paragraph(251731 251831 nil)
> fill-paragraph(nil)
> texinfo-format-refill()
Interesting. Who is the texinfo.el maintainer? I think we should
forward this to him/her.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-02-23 4:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-22 19:27 Vladimir Volovich
1998-02-23 1:23 ` Lars Magne Ingebrigtsen
1998-02-23 2:40 ` SL Baur
1998-02-23 3:14 ` Richard Hoskins
1998-02-23 4:27 ` Lars Magne Ingebrigtsen [this message]
1998-02-23 4:55 ` Richard Hoskins
1998-03-03 2:09 ` Richard Hoskins
1998-03-03 4:30 ` Eze Ogwuma
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=m3u39rrlmh.fsf@sparky.gnus.org \
--to=larsi@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).