From: Doug Bagley <doug@dejanews.com>
Subject: Re: article won't display, errors says article buffer read-only
Date: 12 Mar 1999 09:34:21 -0600 [thread overview]
Message-ID: <yg9sobaoh6q.fsf@acme.dejanews.com> (raw)
In-Reply-To: Doug Bagley's message of "08 Mar 1999 18:02:13 -0600"
Doug Bagley <doug@dejanews.com> writes:
> Using, pgnus-0.80/"20.4 \"Emerald\" XEmacs Lucid", I received the
> following article. When I tried to view it, I got a message in my
> minibuffer saying the article buffer is read-only, and then it beeped
> at me!
Found problem, was:
> (setq gnus-treat-display-picons t)
should be:
(setq gnus-treat-display-picons 'head)
I think it would be better, though, if gnus trapped the error this
caused during display, and still displayed the article, sans
piconification. Is that possible?
Cheers,
Doug
next prev parent reply other threads:[~1999-03-12 15:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 0:02 Doug Bagley
1999-03-09 19:55 ` local variables and Gnus security Robert Epprecht
1999-03-10 9:47 ` Felix Lee
1999-03-10 12:12 ` Robert Epprecht
1999-03-11 17:44 ` Per Abrahamsen
1999-03-11 20:29 ` Karl Eichwalder
1999-03-11 21:56 ` Felix Lee
1999-03-12 11:35 ` Jan Vroonhof
1999-03-14 16:08 ` Lars Magne Ingebrigtsen
1999-03-10 13:42 ` Per Abrahamsen
1999-03-10 18:52 ` François Pinard
1999-03-10 19:04 ` François Pinard
1999-03-11 15:37 ` empiric
1999-03-11 15:55 ` Kai.Grossjohann
1999-03-11 18:01 ` Hallvard B Furuseth
1999-03-10 20:01 ` Alan Shutko
1999-03-10 21:55 ` Robert Epprecht
1999-03-14 16:04 ` Lars Magne Ingebrigtsen
1999-03-12 15:34 ` Doug Bagley [this message]
1999-03-14 16:03 ` article won't display, errors says article buffer read-only 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=yg9sobaoh6q.fsf@acme.dejanews.com \
--to=doug@dejanews.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).