From: Harry Putnam <hgp@sbcglobal.net>
Subject: Re: Strange retreival behavior
Date: Thu, 02 Jan 2003 21:48:32 -0800 [thread overview]
Message-ID: <m2znqirdfz.fsf@sbcglobal.net> (raw)
In-Reply-To: <m37kdo3dio.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <hgp@sbcglobal.net> writes:
>
>> I've seen that in the past too and knew about the off on trick. This
>> is different. There is no hang. The process flashes by as if it had
>> been done but the groups are not refreshed. Pressin M-g on
>> individual groups will refresh them.
>
> Hm... Could you try moving a couple of these groups to, say, level 1
> and see whether that makes any difference?
This was the same problem posted under:
From: Harry Putnam <hgp@sbcglobal.net>
Subject: get-new-news misbehaving?
Newsgroups: gnu.emacs.gnus
Date: Thu, 02 Jan 2003 05:05:43 GMT
Message-ID: <m2adikcnqb.fsf@sbcglobal.net>
Your suggestion there was to set `nntp-server-list-active-group' to
nil.
I did that and it cured my problem. So apparently server related.
prev parent reply other threads:[~2003-01-03 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 2:42 Harry Putnam
2002-12-31 12:47 ` Frank Schmitt
2003-01-01 16:02 ` Harry Putnam
2003-01-01 18:56 ` Lars Magne Ingebrigtsen
2003-01-03 5:48 ` Harry Putnam [this message]
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=m2znqirdfz.fsf@sbcglobal.net \
--to=hgp@sbcglobal.net \
/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).