From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Enabling gnus-delay by default?
Date: Sat, 29 Sep 2001 21:17:41 +0200 [thread overview]
Message-ID: <vafn13dx0ve.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <iluofo3m8to.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 22 Sep 2001 19:30:59 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Wouldn't it be nice if the gnus-delay package was enabled by default?
I think I've now covered almost everything. The only statement that's
executed by gnus-delay-initialize which is still missing is the
following:
(add-hook 'gnus-get-new-news-hook 'gnus-delay-send-drafts)
The question is, how to do this? Should I just invoke
gnus-delay-send-drafts in the appropriate places directly? (Maybe
conditional on a gnus-delay variable.) Or should the above add-hook
be put in some *.el file? In which *.el file?
Hm. If the above add-hook is executed, then gnus-delay.el will be
loaded pretty soon, so all this autoload stuff seems a bit like
shooting a sparrow with a cannon.¹ But on the other hand, requiring a
package is not allowed to actually do anything, so I would be
violating the coding conventions if I were to put the add-hook
statement at the top level in gnus-delay.el.
Argh.
Help!
kai
¹ I think I've asked before what is the English idiom for this...
--
Abort this operation? [OK] [Cancel]
next prev parent reply other threads:[~2001-09-29 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 17:30 Simon Josefsson
2001-09-22 21:32 ` Kai Großjohann
2001-09-22 23:01 ` Simon Josefsson
2001-09-29 19:07 ` Kai Großjohann
2001-09-22 23:23 ` Henrik Enberg
2001-09-29 19:08 ` Kai Großjohann
2001-09-29 19:17 ` Kai Großjohann [this message]
2001-09-30 7:38 ` Norbert Koch
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=vafn13dx0ve.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).