Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Sat, 26 Mar 2011 08:45:15 +0100	[thread overview]
Message-ID: <rpvcz6gwac.fsf@news.eternal-september.org> (raw)
In-Reply-To: <871v1uaopg.fsf@topper.koldfront.dk> ("Adam \=\?utf-8\?Q\?Sj\?\= \=\?utf-8\?Q\?\=C3\=B8gren\=22's\?\= message of "Fri, 25 Mar 2011 22:13:15 +0100")

asjo@koldfront.dk (Adam Sjøgren) writes:

> On Fri, 25 Mar 2011 21:05:42 +0000, Eric wrote:
>
>> Adam, thanks for the pointer to the relevant place in the manual.  My
>> guess was basically completely wrong.  Oh well...
>
>> However, I am not sure the documentation really explains anything at
>> all.
>
> How did you then get to the understanding that you were wrong, then?
>
>> It's the kind of documentation that makes sense if you already know
>> what it is telling you and otherwise just sounds like a circular
>> definition... and, unfortunately, there are quite a few sections like
>> this in the gnus manual.
>
> I am sure suggestions for improvements are very welcome!
>
> What I got from reading it is that groups from servers in select-method
> and secondary-select-methods are called native and other groups are
> called foreign. Seems quite straightforward?
>

Except they the are not. Since the gnus-activate-foreign-newsgroups
applies to groups created from secondary select methods.


>> In any case, this definitely doesn't help me (or the OP maybe)
>> understand why the default activation level for native groups is 6 and
>> for foreign is 4; and what about secondary...?  And how any of this
>> relates to agents?
>
> I don't use any of those thingamajigs, so I haven't got the foggiest.
> Sorry I can't be of any help.

If you had, maybe you could understand the issue above about the foreign
groups naming convention.

>
>   Best regards,
>
>     Adam

-- 
☘ http://www.shamrockirishbar.com, http://splash-of-open-sauce.blogspot.com/ http://www.richardriley.net



  reply	other threads:[~2011-03-26  7:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 12:18 Richard Riley
2011-03-24 13:55 ` Eric S Fraga
2011-03-25 10:53   ` Richard Riley
2011-03-25 12:03     ` Eric S Fraga
2011-03-25 15:04       ` Richard Riley
2011-03-25 15:23         ` Richard Riley
2011-03-25 18:34           ` Richard Riley
2011-03-25 15:58         ` Eric S Fraga
2011-03-25 19:21           ` Adam Sjøgren
2011-03-25 21:05             ` Eric S Fraga
2011-03-25 21:13               ` Adam Sjøgren
2011-03-26  7:45                 ` Richard Riley [this message]
2011-03-26 12:47                   ` Adam Sjøgren
2011-03-27  7:15                     ` Richard Riley
2011-03-27  7:25                     ` Richard Riley
2011-03-27 17:38                 ` Eric S Fraga
2011-03-28 15:03                   ` Richard Riley
2011-03-28 17:07                     ` Eric S Fraga
2011-03-28 16:33                       ` Richard Riley
2011-03-28 18:13                         ` Eric S Fraga
2011-03-29  7:26                           ` Richard Riley
2011-03-29 17:06                             ` Eric S Fraga
2011-03-26  7:43               ` Richard Riley

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=rpvcz6gwac.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --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).