Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Scanning of nnimap groups during gnus-group-get-new-news?
Date: Wed, 16 Aug 2000 10:16:01 +0200	[thread overview]
Message-ID: <vaf3dk5iptq.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Lloyd Zusman's message of "15 Aug 2000 21:08:31 -0400"

On 15 Aug 2000, Lloyd Zusman wrote:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
>> On 11 Aug 2000, Lloyd Zusman wrote:
>> 
>> > Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> > 
>> >> Lloyd Zusman <ljz@asfast.com> writes:
>> >> 
>> >> > Is there a setting that I can use to force my `nnimap' groups
>> >> > to be scanned for new mail every time I type the `g' command
>> >> > (`gnus-group-get-new-news') while in the Group buffer?
>> >> 
>> >> Make sure that your nnimap groups are on a lower level than
>> >> `gnus-save-killed-list'.
>> > 
>> > [ ... ]
>> 
>> I think that Lars means gnus-level-killed, which appears to be 9 by
>> default.
> 
> Ah ... OK.  Well, my nnimap groups are indeed on a lower level than
> `gnus-level-killed'.  It's 9 for me by default and my nnimap group
> is at level 2.  So unfortunately, this does not seem to be the cause
> of the problem.  :(

Well, err.  Level 1 means very important, level 9 means very
unimportant.  But intuitively, a higher level might mean important.
There is a conflict between importantness and the numbers.  Very
confusing.

Maybe it helps if you set the group level to a number greater than or
equal to 9?

kai
-- 
I like BOTH kinds of music.



  reply	other threads:[~2000-08-16  8:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-29 19:24 Lloyd Zusman
2000-08-10 20:50 ` Lars Magne Ingebrigtsen
2000-08-11 22:31   ` Lloyd Zusman
2000-08-13 16:10     ` Kai Großjohann
2000-08-16  1:08       ` Lloyd Zusman
2000-08-16  8:16         ` Kai Großjohann [this message]
2000-08-16 23:05           ` 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=vaf3dk5iptq.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).