From: Tassilo Horn <tassilo@member.fsf.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Next registry error
Date: Thu, 21 Apr 2011 17:51:41 +0200 [thread overview]
Message-ID: <8762q7r4aa.fsf@member.fsf.org> (raw)
In-Reply-To: <8762q7d52e.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 21 Apr 2011 09:58:33 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
Hi Ted,
> TH> Debugger entered--Lisp error: (wrong-type-argument stringp ("nntp" t))
> TH> string-match(("nntp" t) "nnimap+Fastmail:INBOX")
> TH> byte-code("\b\304.\211.\203.\n@.\305 \v\"\203.\306\307 \"\210\nA\211.\204\b.*\304\207" [list r --cl-dolist-temp-- word nil string-match throw found] 4)
> TH> gnus-grep-in-list("nnimap+Fastmail:INBOX" (("nntp" t) ("training" t) ("Junk" t)))
> TH> gnus-registry-ignore-group-p("nnimap+Fastmail:INBOX")
>
> Your `gnus-registry-ignored-groups' or
> `nnmail-split-fancy-with-parent-ignore-groups' is
>
> '(("nntp" t) ("training" t) ("Junk" t))
Yes,
> but it should be a list of regexps or nil. I don't think either of
> those variables, especially `gnus-registry-ignored-groups', ever had
> that format. Can you check?
I'm pretty sure it had that format, where t meant ignore matching groups
and nil meant don't ignore.
Oh, and the docs also use that format:
,----[ (info "(gnus)Setup") ]
| (setq
| gnus-registry-split-strategy 'majority
| gnus-registry-ignored-groups '(("nntp" t)
| ("nnrss" t)
| ("spam" t)
| ("train" t))
| gnus-registry-max-entries 500000
| ;; this is the default
| gnus-registry-track-extra '(sender subject))
`----
I'm totally fine with having that variable as a list of regexps, as I
see no reason for saying ("foo" nil). So it's just a question of you
want to make an incompatible change...
Bye,
Tassilo
--
Sent from my Emacs
next prev parent reply other threads:[~2011-04-21 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 6:32 Tassilo Horn
2011-04-21 14:58 ` Ted Zlatanov
2011-04-21 15:51 ` Tassilo Horn [this message]
2011-04-21 16:37 ` Ted Zlatanov
2011-04-22 6:53 ` Tassilo Horn
2011-04-22 13:21 ` Ted Zlatanov
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=8762q7r4aa.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.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).