From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Documentation of gnus-check-new-newsgroups, select methods value
Date: Sat, 02 Jan 2016 19:55:16 +0800 [thread overview]
Message-ID: <87io3c6vrv.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871ta0z03u.fsf@tullinup.koldfront.dk>
asjo@koldfront.dk (Adam Sjøgren) writes:
> The documentation of gnus-check-new-newsgroups does not mention that
> _if_ you set the variable to a list of select methods, then the options
> set on those select methods in gnus-secondary-select-methods will be
> ignored.
>
> Should it?
>
> What lead me to discover this, is that I have had for a long time:
>
> (setq gnus-secondary-select-methods
> '(
> (nnml ""
> (nnir-search-engine notmuch))
> ...
>
> and recently I added:
>
> (setq gnus-check-new-newsgroups '((nnml "")))
>
> Which had the side effect of making nnir-searches on nnml: return no
> results. (Which, by the way, is also misleading - shouldn't nnir say
> "I was not configured to search anything", rather than "I didn't find
> any results"?)
>
> If I change gnus-check-new-newsgroups to '((nnml "" (nnir-search-engine
> notmuch))) searching works again.
>
> Which is nice, but it feels a little, uh, brittle?
That's almost guaranteed not to be how it's supposed to work -- that
shouldn't have anything to do with searching. I don't know the solution,
I'm afraid, but I will add this to my little list of "things that would
be fixed by EIEIO server definitions" :)
Incidentally, why is the server string name empty? Don't people's
servers usually always have a name? Perhaps if you were using '((nnml
"server name")) in `gnus-check-new-newsgroups', it might not break?
Not that that means this isn't a bug...
next prev parent reply other threads:[~2016-01-02 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 11:34 Adam Sjøgren
2016-01-02 11:55 ` Eric Abrahamsen [this message]
2016-01-02 12:17 ` Adam Sjøgren
2016-01-02 13:59 ` Eric Abrahamsen
2016-01-02 14:13 ` Adam Sjøgren
2016-01-04 2:21 ` Eric Abrahamsen
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=87io3c6vrv.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).