From: Ted Zlatanov <tzz@lifelogs.com>
To: <ding@gnus.org>
Subject: Re: auth-source.el rewrite
Date: Tue, 25 Jan 2011 10:59:02 -0600 [thread overview]
Message-ID: <8762tc538p.fsf@lifelogs.com> (raw)
In-Reply-To: <87ipxdlvqd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 24 Jan 2011 15:36:58 -0800")
On Mon, 24 Jan 2011 15:36:58 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Look it over and let me know what you think. I'm still not sure how the
>> creation should work exactly and hope you will tell me how the rewrite
>> "feels," especially considered against the Secrets API.
LI> I've skimmed the code, and it looks very nice to me. But I still
LI> haven't familiarised myself with the Secrets API, so I can't really
LI> comment there...
LI> So should we(*) just alter nnimap to use the new auth-source API and drop
LI> it into git Gnus? Usually the best way to get the feel of how stuff
LI> works is to use it.
LI> *) I.e., you.
I don't want to affect all the people using auth-source.el currently.
Remember it's not just a Gnus facility. So I wanted to get the API
settled before comitting. Michael Albinus will probably know if the API
makes sense in terms of the Secrets API; I think it should couple OK.
The biggest problem is creation IMO. I think each backend will need its
own list of required keys (always including :host, :secret and :user)
and when the search query is not sufficient to fulfill the requirements,
the user will be prompted for those values. It still feels clumsy.
Ted
next prev parent reply other threads:[~2011-01-25 16:59 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 [this message]
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
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=8762tc538p.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).