From: Raja R Harinath <harinath@cs.umn.edu>
Subject: Re: 0.3 and async pre-fetch (and YA bug report)
Date: 02 Aug 1996 01:31:47 +0000 [thread overview]
Message-ID: <d9hgqmfu63.fsf@cs.umn.edu> (raw)
In-Reply-To: Sudish Joseph's message of 01 Aug 1996 19:41:35 -0400
Sudish Joseph <sudish@mindspring.com> writes:
> I'm curious, why isn't anyone else reporting this? Is it that the
> bug is only visible over a slow connect? Has anyone else seen this?
[snipped description/example. Parts of subsequent articles are being
shown in current article buffer]
Yes. I've seen it, for one. It doesn't look like a slow connect
problem, though the slow connect may make it more apparent. I saw it on
a large group (`soc.culture.indian' in fact. ~200 new articles, I was
in about the 75th, after generous use of `n' and `T o T k').
BTW, I got the following backtrace when I did `^' on an article, and the
parent wasn't in the summary buffer.
Signaling: (error "format specifier doesn't match argument type")
format("%s-%d" "gnu.misc.discuss" "<91c2r1ur.fsf@mihalis.demon.co.uk>")
(intern (format "%s-%d" group article))
(assq (intern (format "%s-%d" group article)) gnus-async-article-alist)
gnus-async-prefetched-article-entry("gnu.misc.discuss" "<91c2r1ur.fsf@mihalis.demon.co.uk>")
(let ((entry ...)) (when entry (save-excursion ... ... ... ... ... ... ... t)))
gnus-async-request-fetched-article("gnu.misc.discuss" "<91c2r1ur.fsf@mihalis.demon.co.uk>" #<buffer *Article*>)
gnus-request-article-this-buffer(-1 "gnu.misc.discuss")
gnus-article-prepare(-1 nil)
gnus-summary-display-article(-1 nil)
gnus-summary-goto-article(-1 nil [-1 "Re: BOYCOTT commercial software! (was: NOTSCAPE!)" "" "" "<91c2r1ur.fsf@mihalis.demon.co.uk>" "<4sm43v$jt8@solutions.solon.com>" 0 0 ""])
gnus-summary-refer-article("<91c2r1ur.fsf@mihalis.demon.co.uk>")
gnus-summary-refer-parent-article(1)
call-interactively(gnus-summary-refer-parent-article)
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
next prev parent reply other threads:[~1996-08-02 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-01 23:41 0.3 and async pre-fetch Sudish Joseph
1996-08-02 1:31 ` Raja R Harinath [this message]
1996-08-02 17:35 ` Lars Magne Ingebrigtsen
1996-08-03 0:35 ` Sudish Joseph
1996-08-04 22:09 ` [ patch ] async stuff fix(?) (was Re: 0.3 and async pre-fetch) Sudish Joseph
1996-08-05 0:39 ` Sudish Joseph
1996-08-05 17:11 ` Lars Magne Ingebrigtsen
1996-08-06 6:08 ` Sudish Joseph
1996-08-06 20:51 ` Lars Magne Ingebrigtsen
1996-08-05 18:20 ` Ken Raeburn
1996-08-05 17:00 ` 0.3 and async pre-fetch 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=d9hgqmfu63.fsf@cs.umn.edu \
--to=harinath@cs.umn.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).