From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: gnus-subscribe-topics doesn't seem to work (fixed, kind of)
Date: 16 Mar 2001 00:24:20 -0500 [thread overview]
Message-ID: <87snkethff.fsf@home.com> (raw)
In-Reply-To: <5bpufir4bf.fsf@avocet.cs.rochester.edu> (ShengHuo ZHU's message of "15 Mar 2001 18:38:12 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
> Dmitry Yaitskov <dimas@home.com> writes:
>
>
> [...]
>
> > in my .gnus.el, I saw that gnus-subscribe-topics never got called. It
> > turned out that gnus-group-find-new-groups (what is bound to F in the
> > group buffer) eventually invoked gnus-ask-server-for-new-groups - and
> > that method calls gnus-subscribe-options-newsgroup-method and not
> > gnus-subscribe-newsgroup-method, to subscribe to new groups. I do not
> > understand the logic behind this stuff, so cannot really say what
> > should be the correct fix - but the way it is seems broken to me.
>
> I bet that those groups you mentioned are options newsgroups.
Hm. Now that you say it... and I have looked up "options" in gnus'
help, I do understand what goes on here. Yes, the new groups I'm
talking about are nnfolder groups created by expiring into a group. I
*do* want them to be subscribed automatically (which is what the
"options" group - i.e. a one that matches the
gnus-auto-subscribed-groups regexp - means, right?)... but at the same
time I very much want them to be put in apropriate topics (spec'd by
subscribe parameter). The two behaviors - always subscribing new
groups if match certain criteria and putting newly subscribed groups
in certain place - seem completely unrelated, the fact that they are
kind of mutually exclusive seems broken to me.
So... what is the *correct* way to do that?
<snip>
> > With these two fixes, it all now seems to work.
>
> This is NOT a fix. The topic parameters should be something like
>
> ((subscribe . "nnslashdot:"))
>
> instead of
>
> ((subscribe "nnslashdot:"))
Oops, sorry.
> If you are not sure what it is, use `G c' instead of `G p'.
Thank you. (and if I'm not sure what `G c' is - should I use Outlook
Express instead?... just kidding.)
> ShengHuo
>
>
--
Cheers,
-Dima.
next prev parent reply other threads:[~2001-03-16 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 20:49 gnus-subscribe-topics doesn't seem to work Dmitry Yaitskov
2001-03-15 22:58 ` Kai Großjohann
2001-03-15 23:28 ` gnus-subscribe-topics doesn't seem to work (fixed, kind of) Dmitry Yaitskov
2001-03-15 23:38 ` ShengHuo ZHU
2001-03-16 5:24 ` Dmitry Yaitskov [this message]
2001-03-16 15:57 ` Dmitry Yaitskov
2001-03-15 23:24 ` gnus-subscribe-topics doesn't seem to work ShengHuo ZHU
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=87snkethff.fsf@home.com \
--to=dimas@home.com \
/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).