From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Re: Problem fetching parent article
Date: 21 Feb 2000 19:22:47 -0500 [thread overview]
Message-ID: <vuor9e6uluw.fsf@csa.bu.edu> (raw)
In-Reply-To: Slawek Zak's message of "21 Feb 2000 22:50:56 +0100"
Slawek Zak writes:
: Emerick Rogul <emerick@cs.bu.edu> writes:
:: Hello,
::
:: I've always used '^' in gnus to fetch a parent article, but I've
:: recently noticed it's not working correctly (I'm using the latest gnus
:: from cvs - 5.8.4).
::
:: I went into a newsgroup today and hit ^ to fetch the parent article
:: and I got the "Can't fetch article ..." message. I left the group and
:: and re-entered it to see all of the old messages, and the parent
:: article was in fact still available (and hitting ^ at this point did
:: do the right thing, btw).
::
:: Is this a bug with the current version or have I done something silly
:: in my init files? Anyone else run into anything like this?
: Try (setq gnus-build-sparse-threads 'some). It didn't work for me
: either before I used this setting.
Hmm...I just tried setting that value and I got the same behavior
(can't fetch a parent news article even though I _know_ it hasn't
expired yet). On a whim, I tried running gnus (5.8.4) without any of
my config files loaded and it's also exhibiting this weird behavior.
Bug perhaps? (No, never!... ;-)
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "how young are you, how old am i?
emerick@cs.bu.edu /\/ let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats
next prev parent reply other threads:[~2000-02-22 0:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-21 5:31 Emerick Rogul
2000-02-21 21:50 ` Slawek Zak
2000-02-22 0:22 ` Emerick Rogul [this message]
2000-02-22 0:38 ` Harry Putnam
2000-02-22 1:08 ` Emerick Rogul
2000-02-22 15:17 ` David S. Goldberg
2000-02-22 15:26 ` Karl Kleinpaste
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=vuor9e6uluw.fsf@csa.bu.edu \
--to=emerick@cs.bu.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).