From: Harry Putnam <reader@newsguy.com>
Subject: Re: edit a w3 rendered message
Date: 21 Nov 1999 20:38:58 -0800 [thread overview]
Message-ID: <m3so1zdtst.fsf@satellite.local.lan> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "15 Nov 1999 21:47:16 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > I can save the jpeg files and rewrite the HTML with sed, of course but
> > would rather handle it right in the gnus buffer. However any attempts
> > to edit give the message:
> >
> > "fontifiying article* buffer too big."
>
> Do you have font-lock turned on in the article buffer?
Yes... I have:
(global-font-lock-mode t)
>
> > If one presses "C-g" at this point, you get a buffer that allows
> > editing but cannot be saved. Giving the message:
> > "Wrong type argument: window-configuration-p, nil"
>
> `(setq debug-on-error t)', repeat the bug and mail me the resulting
> backtrace.
Roger Wilco
next prev parent reply other threads:[~1999-11-22 4:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 6:08 Harry Putnam
1999-11-15 20:47 ` Lars Magne Ingebrigtsen
1999-11-22 4:38 ` Harry Putnam [this message]
1999-12-01 19:08 ` Lars Magne Ingebrigtsen
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=m3so1zdtst.fsf@satellite.local.lan \
--to=reader@newsguy.com \
/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).