Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Fri, 25 Mar 2011 20:21:39 +0100	[thread overview]
Message-ID: <8762r79fb0.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87zkojjioy.fsf@ucl.ac.uk>

On Fri, 25 Mar 2011 15:58:21 +0000, Eric wrote:

> Richard Riley <rileyrg@googlemail.com> writes:
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> [...]

>>> I think I do understand.  You may wish to set not only
>>> gnus-activate-level but also gnus-activate-foreign-newsgroups to 5?  It
>>> defaults to 4, I believe.
>> 
>> That works yes! Wow. Thanks!  But "foreign group"? Why are they foreign
>> groups? They are groups attached to nntp servers defined in select
>> methods. Ye gods its complicated ;) ...

> Somebody will correct me but I think /foreign/ groups refer to those
> where the actual content is stored remotely (nntp, nnimap) versus
> locally (nnml, nnmaildir).

The manual says:

,----[ 10.4 Terminology - http://gnus.org/manual/gnus_366.html ]
|  native
|      Gnus will always use one method (and back end) as the native, or
|      default, way of getting news.
| 
|  foreign
|      You can also have any number of foreign groups active at the same
|      time. These are groups that use non-native non-secondary back ends
|      for getting news.
| 
|  secondary
|      Secondary back ends are somewhere half-way between being native and
|      being foreign, but they mostly act like they are native.
`----


  Best regards,

    Adam

-- 
 "This is either madness... or brilliance."                   Adam Sjøgren
 "It's remarkable how often those two traits coincide."  asjo@koldfront.dk




  reply	other threads:[~2011-03-25 19:21 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 [this message]
2011-03-25 21:05             ` Eric S Fraga
2011-03-25 21:13               ` Adam Sjøgren
2011-03-26  7:45                 ` Richard Riley
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=8762r79fb0.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).