From: Michael Albinus <michael.albinus@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: auth-source.el rewrite
Date: Thu, 27 Jan 2011 17:49:25 +0100 [thread overview]
Message-ID: <87mxmm47hm.fsf@gmx.de> (raw)
In-Reply-To: <8739ofxqf8.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 26 Jan 2011 16:15:23 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> I added this option, which seems necessary for extensibility:
>
> :create-extra-keys ((A \"default a\") (B)) means that the extra
> keys A and B will be created when a new entry is created. If
> SPEC had values for A or B, the user will not be prompted, but
> otherwise the user will be prompted for A (with default value as
> given) and for B (with no default).
Is it necessary to pass them as list with the keyword :create-extra-keys?
Just allow them to be added to SPEC, and if they don't belong to the
well known keywords, they are ignored during search, and used during creation.
Something else I've seen during reading: If we create a new secret, we
use the *first* entry in from auth-sources as container. This is not
documented IIRC, but auth-source-user-or-password is implemented like this.
If a key comes with multiple values (like ":host (X Y Z)"), the *last*
value is taken for creation. Sounds like a headache to me. Couldn't we
always use the first entry?
> Ted
Best regards, Michael.
next prev parent reply other threads:[~2011-01-27 16:49 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
2011-01-26 22:15 ` Ted Zlatanov
2011-01-27 16:49 ` Michael Albinus [this message]
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=87mxmm47hm.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).