From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: mail-sources strangeness
Date: 13 Aug 2000 20:42:20 +0200 [thread overview]
Message-ID: <m3bsyx9f5f.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vafk8fxgr49.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> `mail-sources' uses pop3-movemail if nothing is specified, right?
Well, no. :-) If nothing is specified, it kinda calls another
function (well, progn, but in Emacs Lisp there's not much of a
difference) which then calls pop3-movemail.
> So
> the following two behave the same, right?
>
> (setq mail-sources '((pop :user "foo" :server "bar"))
> (setq mail-sources '((pop :user "foo" :server "bar" :function pop3-movemail))
>
> Wrong.
Yup.
> I think there should be a specified protocol for passing the necessary
> information to the function: user name, host name, password, port,
> authentication scheme. It's not clear to me how a function is
> supposed to get at these values, anyway. (Well, there is
> `mail-source-bind' which might do this, but it's not easy to
> understand what that does... Hm. It appears to provide defaults for
> the colon keywords.)
Yup.
> Whichever scheme is chosen, it should be documented, I think. And
> there should be a function which can be put in like `:function foo'
> such that the default behavior is chosen.
Well, OK, but the function will just look like the progn there, with a
defun before it. Emacs Lisp has nice dynamic variables, so they
should be used. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2000-08-13 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-10 21:31 Kai Großjohann
2000-08-13 18:42 ` Lars Magne Ingebrigtsen [this message]
2000-08-13 19:34 ` Kai Großjohann
2000-08-13 19:43 ` Lars Magne Ingebrigtsen
2000-08-14 12:59 ` Kai Großjohann
2000-08-14 17:11 ` Lars Magne Ingebrigtsen
2000-08-14 21:05 ` Kai Großjohann
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=m3bsyx9f5f.fsf@quimbies.gnus.org \
--to=larsi@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).