From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Sun, 27 Mar 2011 18:38:05 +0100 [thread overview]
Message-ID: <87mxkg31mq.fsf@ucl.ac.uk> (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?
Ummmm, I guess the fact that there are three types of groups whereas I
was thinking of only two types...
>> 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!
I would be more than happy to not only make suggestions but also add
text etc. However, the problem is I don't really understand the text
well enough to even begin adding or changing text! Vicious cycle here
(for me).
> 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?
Okay, I didn't get that from the text but I guess that makes sense. It
still doesn't really tell me how or why the distinction is made,
especially between secondary and foreign? How/where are the latter
actually defined?
Anyway, in my case, this distinction does not appear to be anything I
need to worry about. And I think the OP has solved his problem, in the
sense of identifying the boundary conditions for gnus for his use case.
Thanks for the help,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.16
next prev parent reply other threads:[~2011-03-27 17:38 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
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 [this message]
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=87mxkg31mq.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).