From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: Topic-wise subscription of new newsgroups
Date: Tue, 08 Mar 2005 13:10:52 +0100 [thread overview]
Message-ID: <v9ekeqxrqr.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <85mztemsr1.fsf@mail.bn-software.de>
On Tue, Mar 08 2005, Stefan Kamphausen wrote:
> (from ".* <?\\(.+\\)@office-address.example.*" "mail.office.\\1")
[...]
> However, whenever I receive an email of a new colleague (which has no
> group associated) I can only see the new group when I do a
> gnus-find-new-newsgroups manually. But I'd like them so show up
> immediately.
Did you try this suggestion from the manual?
,----[ (info "(gnus)Subscription Methods") ]
| `gnus-subscribe-topics'
| Put the groups into the topic that has a matching `subscribe' topic
| parameter (*note Topic Parameters::). For instance, a `subscribe'
| topic parameter that looks like
|
| "nnslashdot"
|
| will mean that all groups that match that regex will be subscribed
| under that topic.
`----
> My preferred approach would be to use:
> (setq gnus-parameters
> '(("^nnml.*"
> (gnus-show-threads nil)
> (gnus-check-new-newsgroups 'always))
> ))
>
> And while the first setting (gnus-show-threads) is working fine (which
> tells me that the matcher works) the second does nothing.
Finding and subscribing new newsgroups is done at startup or by using
the function `gnus-find-new-newsgroup'. I wouldn't expect that
`gnus-check-new-newsgroups' makes any sense in context of specific
groups or topics.
> I tried this in group and topic parameters (using G p and G c), too,
> but to no avail.
>
> I found the possibility for "always" only in the info file (how do you
> always add these nice boxes??) while it is not in the docstring.
Like the one above?
,----[ C-h f rs-info-boxquote RET ]
| rs-info-boxquote is an interactive Lisp function in `rs-info'.
| (rs-info-boxquote &optional USE-LIST)
|
| Yank text (from an info node), box it and use current info node as title.
| If USE-LIST, the title is taken from `rs-info-title-alist'
| depending on the current newsgroup.
`----
See: http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/misc/rs-info.el
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-03-08 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 8:44 Stefan Kamphausen
2005-03-08 12:10 ` Reiner Steib [this message]
2005-03-08 13:14 ` Stefan Kamphausen
2005-03-08 14:19 ` Reiner Steib
2005-03-08 14:32 ` Stefan Kamphausen
2005-03-08 14:51 ` Tim McNamara
2005-03-08 15:19 ` Stefan Kamphausen
2005-03-08 21:35 ` Tim McNamara
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=v9ekeqxrqr.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+from-uce@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).