From: Adrian Aichner <adrian@xemacs.org>
Subject: How do check for existing/subscribed nndoc group?
Date: Sat, 09 Apr 2005 22:05:20 +0200 [thread overview]
Message-ID: <psx3zpfj.fsf@smtprelay.t-online.de> (raw)
Hi All!
This is some experimental code I came up with.
(message "gnuslog-file %S %ssubscribed to." gnuslog-file
(if
(gnus-gethash
(format "nndoc+%s:%s"
(expand-file-name gnuslog-file)
(file-name-nondirectory gnuslog-file))
gnus-newsrc-hashtb)
"is "
(if (gnus-group-make-doc-group gnuslog-file 'guess)
"has now been "
"could not be ")))
I'm not happy about with it, since checking gnus-newsrc-hashtb looks
too implementation-specific to me.
Is there a better way (in gnus-version "Gnus v5.10.7" if possible)?
Also, is there a distinction between subscribed and unsubscribed nndoc
group?
It didn't seem so according to my experiments.
Another thing:
When I debug above form with
M-f11 runs the command edebug-defun
and gnuslog-file is not in gnus-newsrc-hashtb, then some output of
gnus-group-make-doc-group gets inserted into the source buffer
(gnuslog.el in my case)!
Best regards,
Adrian
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/
reply other threads:[~2005-04-09 20:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=psx3zpfj.fsf@smtprelay.t-online.de \
--to=adrian@xemacs.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).