From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: <ding@gnus.org>
Subject: Re: auth-source.el rewrite
Date: Wed, 26 Jan 2011 14:35:12 -0600 [thread overview]
Message-ID: <877hdrxv27.fsf@lifelogs.com> (raw)
In-Reply-To: <87fwsfihkp.fsf@gmx.de> (Michael Albinus's message of "Wed, 26 Jan 2011 20:35:34 +0100")
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Wed, 26 Jan 2011 20:35:34 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:
MA> Ted Zlatanov <tzz@lifelogs.com> writes:
MA> OK, but short tests help me to understand the API better. And if it
MA> comes to creation of new entries, I would like to *see* how it works.
>>
>> Bah. Now I have to write auth-source-netrc-create before the weekend :)
MA> For the rest, I've played already around. In general, the new API looks
MA> good to me. Appended is a patch for some few minor things I've observed
MA> during the game.
I applied your patch to my copy (attached below).
Regarding caching, I think the cache key will be a serialized version of
SPEC that expires when the file is modified or after a minute. I really
don't like caching this information, though; I'd rather force the client
to cache those results if it makes sense. So I may be annoying and
remove `auth-source-do-cache' and all the related code altogether.
MA> And now waiting for the creation thingie ...
OK, I'll aim for that to be done soon.
Thanks
Ted
[-- Attachment #2: auth-source.el --]
[-- Type: application/emacs-lisp, Size: 37257 bytes --]
next prev parent reply other threads:[~2011-01-26 20:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 2:59 nnimap-username Daiki Ueno
2010-10-25 6:33 ` nnimap-username Reiner Steib
2010-10-25 7:13 ` nnimap-username Daiki Ueno
2010-10-25 18:09 ` auth-source tokens (was: nnimap-username) Ted Zlatanov
2010-10-26 16:56 ` auth-source tokens Ted Zlatanov
2010-10-29 8:04 ` Michael Albinus
2010-10-29 22:15 ` Lars Magne Ingebrigtsen
2010-11-11 16:22 ` Ted Zlatanov
2010-11-14 17:24 ` Michael Albinus
2010-11-15 0:59 ` Ted Zlatanov
2010-11-15 4:47 ` Michael Albinus
2010-11-15 15:14 ` Ted Zlatanov
2010-11-15 16:03 ` Michael Albinus
2011-01-24 17:27 ` auth-source.el rewrite (was: auth-source tokens) Ted Zlatanov
2011-01-24 23:36 ` auth-source.el rewrite Lars Ingebrigtsen
2011-01-25 16:59 ` Ted Zlatanov
2011-01-25 21:09 ` Michael Albinus
2011-01-25 21:42 ` Ted Zlatanov
2011-01-26 8:32 ` Michael Albinus
2011-01-26 17:03 ` Ted Zlatanov
2011-01-26 19:35 ` Michael Albinus
2011-01-26 20:35 ` Ted Zlatanov [this message]
2011-01-26 22:15 ` Ted Zlatanov
2011-01-27 16:49 ` Michael Albinus
2011-01-27 20:20 ` Ted Zlatanov
2011-01-29 14:11 ` Michael Albinus
2011-01-31 2:49 ` Ted Zlatanov
2011-01-31 14:30 ` Michael Albinus
2011-01-31 17:09 ` Ted Zlatanov
2011-01-27 12:35 ` Michael Albinus
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=877hdrxv27.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=michael.albinus@gmx.de \
/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).