From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Using the new auth-source
Date: Fri, 18 Feb 2011 14:22:29 -0600 [thread overview]
Message-ID: <87r5b5w0sa.fsf@lifelogs.com> (raw)
In-Reply-To: <8739nm9qcw.fsf@gnus.org>
On Thu, 17 Feb 2011 15:46:23 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> It's doing two backends, ~/.authinfo.gpg and ~/.authinfo, and since the
>> first doesn't exist, it tries to create it. So it should probably do a
>> two-pass thing without :create to see if any of them return credentials.
LI> I've now implemented this, and it Works For Me. Ted, could you look it
LI> over and fix the bugs I (no doubt) introduced? :-)
I'll take a look ASAP and do the other prompt fixes we discussed, but
probably not today.
Ted
next prev parent reply other threads:[~2011-02-18 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 22:53 Lars Ingebrigtsen
2011-02-17 23:06 ` Lars Ingebrigtsen
2011-02-17 23:46 ` Lars Ingebrigtsen
2011-02-18 10:49 ` Steinar Bang
2011-02-18 11:59 ` Raphael Kubo da Costa
2011-02-18 12:12 ` Katsumi Yamaoka
2011-02-18 12:20 ` Raphael Kubo da Costa
2011-02-18 15:47 ` Raphael Kubo da Costa
2011-02-18 22:09 ` Lars Ingebrigtsen
2011-02-18 20:22 ` Ted Zlatanov [this message]
2011-02-18 9:05 ` Steinar Bang
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=87r5b5w0sa.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).