From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: The `subscribe' topic parameter
Date: 12 Nov 1999 20:05:54 +0100 [thread overview]
Message-ID: <rjhfirwmwd.fsf@feller.dina.kvl.dk> (raw)
I made it customizable. It should probably be mentioned in the Topic
Parameters section in the manual.
With regard to `gnus-subscribe-topics' I couln't find any
documentation of what happens to groups that aren't subscribed by any
topics.
Eh, I can just commit changes for customize support as I see fit,
right?
1999-11-12 Per Abrahamsen <abraham@dina.kvl.dk>
* gnus-cus.el (gnus-group-parameters): Changed from `defcustom' to
`defconst'.
mention that it is both for group and topic parameters.
(gnus-extra-topic-parameters): New constant, including `subscribe'
parameter.
(gnus-extra-group-parameters): New constant.
(gnus-group-customize): Use them.
Index: gnus-cus.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-cus.el,v
retrieving revision 5.14
diff -c -r5.14 gnus-cus.el
*** gnus-cus.el 1999/07/09 19:28:51 5.14
--- gnus-cus.el 1999/11/12 19:01:04
***************
*** 56,62 ****
;;; Group Customization:
! (defcustom gnus-group-parameters
'((to-address (gnus-email-address :tag "To Address") "\
This will be used when doing followups and posts.
--- 56,62 ----
;;; Group Customization:
! (defconst gnus-group-parameters
'((to-address (gnus-email-address :tag "To Address") "\
This will be used when doing followups and posts.
***************
*** 238,249 ****
gnus-emphasis-highlight-words))))
"highlight regexps.
See gnus-emphasis-alist."))
! "Alist of valid group parameters.
Each entry has the form (NAME TYPE DOC), where NAME is the parameter
itself (a symbol), TYPE is the parameters type (a sexp widget), and
DOC is a documentation string for the parameter.")
(defvar gnus-custom-params)
(defvar gnus-custom-method)
(defvar gnus-custom-group)
--- 238,266 ----
gnus-emphasis-highlight-words))))
"highlight regexps.
See gnus-emphasis-alist."))
! "Alist of valid group or topic parameters.
Each entry has the form (NAME TYPE DOC), where NAME is the parameter
itself (a symbol), TYPE is the parameters type (a sexp widget), and
DOC is a documentation string for the parameter.")
+ (defconst gnus-extra-topic-parameters
+ '((subscribe (regexp :tag "Subscribe") "\
+ If `gnus-subscribe-newsgroup-method' is set to
+ `gnus-subscribe-topics', new groups that matches this regexp will
+ automatically be subscribed to this topic"))
+ "Alist of topic parameters that are not also group parameters.
+
+ Each entry has the form (NAME TYPE DOC), where NAME is the parameter
+ itself (a symbol), TYPE is the parameters type (a sexp widget), and
+ DOC is a documentation string for the parameter.")
+
+ (defconst gnus-extra-group-parameters nil
+ "Alist of group parameters that are not also topic parameters.
+
+ Each entry has the form (NAME TYPE DOC), where NAME is the parameter
+ itself (a symbol), TYPE is the parameters type (a sexp widget), and
+ DOC is a documentation string for the parameter.")
(defvar gnus-custom-params)
(defvar gnus-custom-method)
(defvar gnus-custom-group)
***************
*** 258,264 ****
:doc ,(nth 2 entry)
(const :format "" ,(nth 0 entry))
,(nth 1 entry)))
! gnus-group-parameters)))
(unless (or group topic)
(error "No group on current line"))
(when (and group topic)
--- 275,284 ----
:doc ,(nth 2 entry)
(const :format "" ,(nth 0 entry))
,(nth 1 entry)))
! (append gnus-group-parameters
! (if group
! gnus-extra-group-parameters
! gnus-extra-topic-parameters)))))
(unless (or group topic)
(error "No group on current line"))
(when (and group topic)
next reply other threads:[~1999-11-12 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 19:05 Per Abrahamsen [this message]
1999-11-12 19:25 ` Lars Magne Ingebrigtsen
1999-11-12 19:33 ` Per Abrahamsen
1999-12-01 13:23 ` Lars Magne Ingebrigtsen
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=rjhfirwmwd.fsf@feller.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).