From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: should auth-source cache false results?
Date: Wed, 23 Feb 2011 09:07:10 -0600 [thread overview]
Message-ID: <87k4gqokm9.fsf@lifelogs.com> (raw)
In-Reply-To: <87wrkr40bo.fsf@gnus.org>
On Wed, 23 Feb 2011 00:33:31 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> In practice this is, I think, a bad idea (I tried it out). If the user
>> adds entries externally, he will be mystified and won't necessarily know
>> about auth-source-forget*. So instead I cache all netrc searches now.
LI> If the .authinfo file changes, then auth-source should forget those
LI> entries automatically, shouldn't it?
Yeah. I must have screwed it up. But now the other problem is that
false results and no results look the same, being nil. How do I store
that semantic distinction?
Ted
next prev parent reply other threads:[~2011-02-23 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 12:06 Ted Zlatanov
2011-02-17 13:41 ` Ted Zlatanov
2011-02-17 22:41 ` Lars Ingebrigtsen
2011-02-22 20:53 ` Ted Zlatanov
2011-02-23 8:33 ` Lars Ingebrigtsen
2011-02-23 15:07 ` Ted Zlatanov [this message]
2011-02-25 3:05 ` Lars Ingebrigtsen
2011-02-25 21:32 ` Ted Zlatanov
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=87k4gqokm9.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).