From: craffert@ml.com (Colin Rafferty)
Subject: gnus-single-article-buffer broken
Date: 12 Feb 1996 16:10:56 -0500 [thread overview]
Message-ID: <ocrivhc2qsf.fsf@spssunp.ml.com> (raw)
Howdy-
I have just upgraded from 0.32 to 0.38. I am having been seeing the
same problem in both.
(setq gnus-single-article-buffer nil) does not seem to be fully
implemented. While there are multiple article buffers with names like
"*Article nnml:list.ding", there is only one " *Original Article*"
buffer, where they should be named " *Original Article nnml:list.ding*".
This wreaks havok with many facets of Gnus. There are, in fact, two
classes of errors that come out of this:
1. Handling an article seldoms works. gnus-summary-enter-digest-group
and caching articles (setq gnus-use-cache t) never work correctly.
2. Reading two groups at once is practically impossible. Since both are
trying to use the same original article buffer, and each assumes that
it has exclusive control over it, horrible things happen.
Although I know that this is not the greatest bug report, it is very
easy to reproduce at home. Just add the following line to the end of
your .gnus file, and try to read two groups at once:
(setq gnus-single-article-buffer nil)
By the way, I love Gnus.
--
Colin Rafferty
Violate the Communications Decency Act.
"...shit, piss, fuck, cunt, cocksucker, mother-fucker, and tits."
-FCC v. Pacifica Foundation 438 U.S. 726 (1978)
reply other threads:[~1996-02-12 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ocrivhc2qsf.fsf@spssunp.ml.com \
--to=craffert@ml.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).