From: Ted Zlatanov <tzz@lifelogs.com>
To: XeCycle <XeCycle@Gmail.com>
Cc: ding@gnus.org
Subject: Re: Bug: auth-sources not set before retrieving authinfo
Date: Wed, 18 Jul 2012 10:13:30 -0400 [thread overview]
Message-ID: <877gu1nomt.fsf@lifelogs.com> (raw)
In-Reply-To: <871ulmscdd.fsf@xc.laptop> (XeCycle@gmail.com's message of "Mon, 11 Jun 2012 12:26:06 +0800")
On Mon, 11 Jun 2012 12:26:06 +0800 XeCycle <XeCycle@Gmail.com> wrote:
X> Ted Zlatanov <tzz@lifelogs.com> writes:
X> [...]
>> You can also structure `auth-sources' so a specific host is found in
>> ~/.authinfo but all others come from ~/.authinfo.gpg.
>>
>> First in the list, put the ~/.authinfo entry, and add an extra parameter
>> "host: regex" with `M-x customize-variable'. The equivalent Lisp:
>>
>> #+begin_src lisp
>> (setq auth-sources '((:source "~/.authinfo" :host "yourhost" :port t)
>> (:source "~/.authinfo.gpg" :host t :port t)))
>>
>> #+end_src
>>
>> Let me know if it works OK for you or not.
X> Sadly it doesn't. It seems to try all sources.
X> I've set it to this:
X> (setq auth-sources '((:source "/dev/null" :host "localhost")
X> (:source "~/.authinfo.gpg" :host t)))
X> It still asks me for that.
It will search `auth-sources' until it finds a match; the second entry
has :host t so it's considered in the search. We don't have the ability
to say "don't search for host X" yet. So you'll have to make a file
with an entry for localhost and put it first in auth-sources.
I think this is a pretty unusual case and I hope you agree. If not I
can look into supporting it better.
Ted
next prev parent reply other threads:[~2012-07-18 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 8:56 XeCycle
2012-06-06 3:55 ` XeCycle
2012-12-23 2:35 ` Ted Zlatanov
2012-06-10 19:02 ` Lars Magne Ingebrigtsen
2012-06-10 19:09 ` Ted Zlatanov
2012-06-11 4:26 ` XeCycle
2012-07-18 14:13 ` Ted Zlatanov [this message]
2012-12-23 2:37 ` Ted Zlatanov
2012-06-11 4:03 ` XeCycle
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=877gu1nomt.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=XeCycle@Gmail.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).