From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Sun, 27 Mar 2011 09:25:14 +0200 [thread overview]
Message-ID: <8zlj01vxd1.fsf@news.eternal-september.org> (raw)
In-Reply-To: <877hbm9hh5.fsf@topper.koldfront.dk> ("Adam \=\?utf-8\?Q\?Sj\?\= \=\?utf-8\?Q\?\=C3\=B8gren\=22's\?\= message of "Sat, 26 Mar 2011 13:47:02 +0100")
asjo@koldfront.dk (Adam Sjøgren) writes:
> On Sat, 26 Mar 2011 08:45:15 +0100, Richard wrote:
>
>> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>>> 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.
>
> So the manual is wrong and you have a better understanding - which puts
> you in an excellent position to improve the manual. Thanks in advance!
>
> Best regards,
>
> Adam
This discussion is to clarify how it is, how it should or maybe just how
to improve it. If I knew how it should and could work for the masses
perhaps I could do this. As it is I see this discussion with Eric as a
valuable "real use" exercise and discussion in honing Gnus to work
better for the end user. I dont have the solutions just on my own
limited experience so changing the manual would seem a tad premature
considering its me learning how gnus works. It never ceases to amaze me
how others use the same features. All I know is that at this minute
using agent in a cost restricted "mostly disconnected" arena its
confusing and a few things simply dont work (see multiple IMAP selection
methods mentioned earlier).
In the case above how would I correct the manual? Perhaps the code is
wrong? Perhaps the concept is wrong. I dont know. What I do know is that
its not clear and the discussion with Eric is helping to clarify end
user use cases which might lead to either bug fixes, manual changes
and/or functionality redesign.
Possibly you have some comments relevant to the agent and activation
levels which might help?
Thanks in advance!
next prev parent reply other threads:[~2011-03-27 7:25 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 [this message]
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=8zlj01vxd1.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).