From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: gnus-delay problem
Date: Tue, 29 Apr 2003 17:17:45 +0200 [thread overview]
Message-ID: <84k7dd9vty.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <m3bryqb5g0.fsf@defun.localdomain> (Jesper Harder's message of "Tue, 29 Apr 2003 00:52:31 +0200")
Jesper Harder <harder@myrealbox.com> writes:
> The problem appears to be the code in `gnus-delay-article' which is
> responsible for creating the delay group:
>
> ;; If group does not exist, create it.
> (let ((group (format "nndraft:%s" gnus-delay-group)))
> (unless (gnus-gethash group gnus-newsrc-hashtb)
> (nndraft-request-create-group gnus-delay-group)
> ;; Make it active.
> (gnus-set-active group (cons 1 0))))
>
> The directory for the delay group is created, but Gnus doesn't find
> the group and it isn't entered in my `gnus-newsrc-hashtb'. After
> executing the above
>
> (gnus-gethash group gnus-newsrc-hashtb)
>
> still returns nil.
I think I snarfed this code from the spot where nndraft:drafts is
created. So if that code has changed, the gnus-delay code may have
to be changed, too.
I know it was a stupid thing to do to copy and paste things that I
didn't understand.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-29 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 22:52 Jesper Harder
2003-04-29 15:17 ` Kai Großjohann [this message]
2003-04-29 15:26 ` Kai Großjohann
2003-04-29 17:56 ` Jesper Harder
2003-04-30 14:53 ` Kai Großjohann
-- strict thread matches above, loose matches on Subject: below --
2003-02-03 10:40 Kai Großjohann
2003-02-04 5:43 ` Katsumi Yamaoka
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=84k7dd9vty.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).