From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: inheritatively specifying group parameters (was: Where are group parameters stored?)
Date: Wed, 13 Jul 2011 22:50:53 +0200 [thread overview]
Message-ID: <877h7l3nwy.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <87liw22bfi.fsf@yun.yagibdah.de>
lee <lee@yun.yagibdah.de> writes:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> lee <lee@yun.yagibdah.de> writes:
>>
>> Hi Lee,
>>
>>>> (setq gnus-parameters
>>>> `((,(rx (or "emacs" "gnus")) ;; 1)
>>>> (gnus-button-emacs-level 10))
>
> [...]
> Inheritance can be very useful to me because without it, I have a lot of
> repetitive entries in my list of gnus-parameters.
>
How comes that the following doesn't work:
(setq gnus-parameters
'((,(rx (or "bogus" "mail"))
(gnus-show-threads nil)
(gnus-use-scoring nil)
(gnus-article-sort-functions '((not gnus-article-sort-by-date)))
(display . [not expire])
(gcc-self . "mail.sent")
(gnus-summary-line-format
":%U%R%z%I(%5L) %(%[%-23,23f%]%) %11&user-date; '%s\n"))
))
It gives me a backtrace when starting gnus:
,----
| Debugger entered--Lisp error: (wrong-type-argument stringp (\, (rx (or "bogus" "mail"))))
| string-match((\, (rx (or "bogus" "mail"))) "nnmaildir+temp:copy")
| gnus-group-fast-parameter("nnmaildir+temp:copy" read-only allow-list)
| gnus-group-find-parameter("nnmaildir+temp:copy" read-only allow-list)
| nnmaildir--param("nnmaildir+temp:copy" read-only)
| byte-code([...])
| nnmaildir--scan("copy" nil [0] (nnmaildir "temp" (directory "~/md-access")) "/home/lee/md-access/" directory-files)
| nnmaildir-request-scan(find-new-groups "temp")
| nnmaildir-request-list("temp")
| nnmaildir-request-newgroups("Wed, 13 Jul 2011 22:27:18 +0200" "temp")
| gnus-request-newgroups("Wed, 13 Jul 2011 22:27:18 +0200" (nnmaildir "temp" (directory "~/md-access")))
| gnus-ask-server-for-new-groups()
| gnus-find-new-newsgroups()
| gnus-setup-news(nil nil nil)
| byte-code([...])
| gnus-1(nil nil nil)
| gnus(nil)
| call-interactively(gnus t nil)
| execute-extended-command(nil)
| call-interactively(execute-extended-command nil nil)
`----
next prev parent reply other threads:[~2011-07-13 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:31 Where are group parameters stored? Dave Abrahams
2011-07-08 13:40 ` Tassilo Horn
2011-07-12 17:21 ` Dave Abrahams
2011-07-12 18:26 ` Tassilo Horn
2011-07-13 0:54 ` lee
2011-07-13 7:13 ` Tassilo Horn
2011-07-13 20:05 ` lee
2011-07-13 20:50 ` lee [this message]
2011-07-13 21:18 ` inheritatively specifying group parameters Peter Münster
2011-07-14 6:16 ` Tassilo Horn
2011-07-14 16:05 ` lee
2011-07-14 6:19 ` Where are group parameters stored? Tassilo Horn
2011-07-14 16:25 ` lee
2011-07-14 18:26 ` Tassilo Horn
2011-07-14 19:18 ` lee
2011-07-14 17:20 ` Dave Abrahams
2011-07-13 5:23 ` Steinar Bang
2011-07-19 16:49 ` Lars Magne Ingebrigtsen
2011-07-13 5:18 ` Steinar Bang
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=877h7l3nwy.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--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).