From: drkm <usenet@fgeorges.org>
Subject: Re: check mail config in init.el
Date: Mon, 10 Jan 2005 13:08:11 +0100 [thread overview]
Message-ID: <wku0pp1o7o.fsf@fgeorges.org> (raw)
In-Reply-To: <sm592251.fsf@libero.it>
attila <startnow@libero.it> writes:
> drkm <usenet@fgeorges.org> writes:
>> attila <startnow@libero.it> writes:
>>> but I would want to put it in the init.el.
>> Why?
> I want a single file of configuration.
It sounds strange to me. Why not keep these things in different
files? It's more easily maintainable, Gnus-things are loaded only if
you start it, etc.
But if you want, there is no problem. You define two functions, no
problem. You call `gnus-demon-add-handler'. So you have to require
gnus-demon, or gnus (which autoload it). Something like this would be
ok:
(defun ...
(defun ...
(require 'gnus-demon)
(gnus-demon-add-handler 'gnus-demon-scan-and-update 5 nil)
Or:
(defun ...
(defun ...
(eval-after-load 'gnus
'(progn
(require 'gnus-demon)
(gnus-demon-add-handler 'gnus-demon-scan-and-update 5 nil)))
So the PROGN form will be eval'ed only after Gnus will be loaded.
The disadvantage with the first way is that it require gnus-demon at
the Emacs load time.
--drkm
next parent reply other threads:[~2005-01-10 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <is66wakk.fsf@libero.it>
[not found] ` <wk7jmm2rqi.fsf@fgeorges.org>
[not found] ` <sm592251.fsf@libero.it>
2005-01-10 12:08 ` drkm [this message]
[not found] ` <r7ktl946.fsf@libero.it>
2005-01-10 13:19 ` Aidan Kehoe
2005-01-10 23:22 ` drkm
2005-01-10 23:55 ` Aidan Kehoe
[not found] ` <v9fz19pdmw.fsf@marauder.physik.uni-ulm.de>
[not found] ` <ekgsfm2g.fsf@libero.it>
[not found] ` <wk6522v9ma.fsf@fgeorges.org>
[not found] ` <brbuichw.fsf@libero.it>
2005-01-13 0:45 ` drkm
[not found] ` <u0pllqmp.fsf@libero.it>
2005-01-13 8:11 ` attila
2005-01-13 16:32 ` drkm
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=wku0pp1o7o.fsf@fgeorges.org \
--to=usenet@fgeorges.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).