From: Xavier Maillard <zedek@gnu-rox.org>
Cc: ding@gnus.org
Subject: Re: Looking for the variable that controls newsgroup scanning
Date: Thu, 24 Jul 2003 19:33:40 +0200 [thread overview]
Message-ID: <plop87oezjkex7.fsf@gnu-rox.org> (raw)
In-Reply-To: <adb5ywg3.fsf@asfast.com> (Lloyd Zusman's message of "Wed, 23 Jul 2003 13:39:08 -0400")
[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]
On 23 jui 2003, Lloyd Zusman outgrape:
> I'm making use of several nnimap groups, each of which being defined
> within `gnus-secondary-select-methods'. As far as I can tell, each
> one is defined identically, the only difference being their names.
>
> However, only the first of these three gets updated during
> `gnus-group-get-new-news'. I need to enter the other two and
> specifically invoke `gnus-summary-rescan-group' in order for them to
> notice any new mail that might have arrived.
>
> I suspect that ages ago, I might have set some sort of variable which
> prevents all but the first nnimap group from being scanned during
> `gnus-group-get-new-news', but I can't for the life of me recall what
> I might have done, nor have I been able to find anything within my
> setup that seems to affect this behavior.
>
> Could any of you suggest some possible variables or settings that
> might control this?
Maybe a clue : do you take advantage of (*the so cool*) (un)plug
feature ?
Ok forget about that it can't be the source of your problems ;)
Maybe you have defined an alist of servers not to be checked during a
g-g-g-n-n ? (at least automatically)
Last but not least how do you call the function ?
This is the relevant info section for g-g-g-n-n :
,----[ C-h f gnus-group-get-new-news RET ]
| gnus-group-get-new-news is an interactive compiled Lisp function in `gnus-group'.
| (gnus-group-get-new-news &optional ARG)
|
| Get newly arrived articles.
| If ARG is a number, it specifies which levels you are interested in
| re-scanning. If ARG is non-nil and not a number, this will force
| "hard" re-reading of the active files from all servers.
|
| [back]
`----
Maybe your groups are not on the same level ? Maybe you inhibit some
hooks such as gnus-get-top-news-hook or gnus-get-new-news-hook ?
Sorry if I am not clear but I am still a n00b at trying to help people
getting out of their problems :)
> Thanks in advance.
zeDek
--
"Breaking Windows isn't just for kids anymore..."
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-07-24 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 17:39 Lloyd Zusman
2003-07-24 17:33 ` Xavier Maillard [this message]
2003-07-24 23:12 ` Lloyd Zusman
2003-07-25 5:52 ` Xavier Maillard
2003-07-26 13:55 ` Lloyd Zusman
2003-07-26 13:04 ` Kai Großjohann
2003-07-26 14:00 ` Lloyd Zusman
2003-07-27 9:28 ` Kai Großjohann
2003-07-28 23:25 ` Lloyd Zusman
2003-07-29 5:50 ` Xavier Maillard
2003-07-29 19:33 ` Lloyd Zusman
2003-07-29 21:11 ` Xavier Maillard
2003-08-02 23:36 ` Solved! (was: Looking for the variable that controls newsgroup scanning) Lloyd Zusman
2003-08-03 11:04 ` Solved! Simon Josefsson
2003-08-03 13:37 ` Solved! Lloyd Zusman
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=plop87oezjkex7.fsf@gnu-rox.org \
--to=zedek@gnu-rox.org \
--cc=ding@gnus.org \
/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).