From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: auth-source unnecessary prompting
Date: Tue, 22 Feb 2011 15:57:46 -0600 [thread overview]
Message-ID: <878vx7ybol.fsf@lifelogs.com> (raw)
In-Reply-To: <m3zkprgfpl.fsf@neo.luffy.cx>
On Sun, 20 Feb 2011 11:31:18 +0100 Vincent Bernat <bernat@luffy.cx> wrote:
VB> I also share this opinion. Neither the server prompt, nor the port
VB> prompt is necessary. If possible, I would rather skip the proposition to
VB> save my credentials into authinfo/authinfo.gpg.
I've gotten pretty close to what you want. You can choose at this prompt:
"Add to file ~/.authinfo.gpg? (y)es/(n)o but use it/(e)dit line/(s)kip file:"
where picking ?n has that effect of "use but don't save it."
I'm not sure if we want a auth-source-create-behavior variable that can
be customized to 'nosaves, so it will be as if you always enter ?n at
the prompt above. To me that seems an unnecessary refinement but if you
disagree please let me know.
Ted
next prev parent reply other threads:[~2011-02-22 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 5:44 nyc4bos
2011-02-20 10:31 ` Vincent Bernat
2011-02-22 21:57 ` Ted Zlatanov [this message]
2011-02-28 23:23 ` Vincent Bernat
2011-02-21 0:02 ` Lars Ingebrigtsen
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=878vx7ybol.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).