From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: bug-gnu-emacs@gnu.org
Subject: Re: bug#8050: Gnus does not connect to my IMAP server any more
Date: Tue, 22 Feb 2011 15:51:29 -0600 [thread overview]
Message-ID: <87lj17ybz2.fsf@lifelogs.com> (raw)
In-Reply-To: <jwvd3mpq8fq.fsf-monnier+emacs@gnu.org>
On Fri, 18 Feb 2011 17:43:13 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
SM> The previous prompt included the ~/.authinfo.gpg file name which
SM> I thought was good. On the contrary, the hostname info seems redundant
SM> since it's already been displayed by the previous 2 prompts.
>> where `s' shows the line we will add with the password replaced by ****?
SM> Here are some ways to handle the "showing the line":
SM> 1- show it in the prompt: loud, noisy, and worst of all, shows the
SM> password in the clear, right after you entered it via `read-passwd'
SM> which was careful to keep it hidden.
SM> 2- Add an `s' option to the prompt.
SM> 3- Add a second prompt (when if the user selected `y') to confirm the
SM> actual text that will be saved. Can be kind of a pain for the user,
SM> but presumably, password aren't saved all the time.
SM> 4- not show it at all, let the user visit the file afterwards to see
SM> what happened if he wants to.
SM> 1 is out. 2 seems like a lot of trouble compared to using y-or-n-p
SM> (tho, if you add an `N' option anyway to remember not to prompt next
SM> time, the extra work is already done). 3 might be a bit annoying to
SM> some of the users (especially those who want to save the password but
SM> don't want to have it displayed). 4 seemed sufficient to me, but
SM> apparently YMMV.
SM> So yes, I'd vote for 2 or 4 (as the coder, I'd choose 4 ;-)
I did 2+3, asking as follows:
Add to file ~/.authinfo.gpg? (y)es/(n)o but use it/(e)dit line/(s)kip file: s
where ?e uses read-string. I distinguish between ?n to say "don't save
but keep this info" and ?s to say "skip this file, I want to add to the
next one". So it's one prompt, plus ?e for those who want to ensure
the data is saved correctly.
Ted
next prev parent reply other threads:[~2011-02-22 21:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12.1297821996.25725.bug-gnu-emacs@gnu.org>
2011-02-16 18:29 ` Ted Zlatanov
2011-02-16 21:22 ` Stefan Monnier
2011-02-16 21:34 ` Michael Albinus
2011-02-16 22:08 ` Ted Zlatanov
2011-02-18 0:24 ` Lars Ingebrigtsen
2011-02-18 2:37 ` Stefan Monnier
2011-02-18 8:19 ` Lars Ingebrigtsen
2011-02-18 10:54 ` Steinar Bang
2011-02-18 20:16 ` Ted Zlatanov
2011-02-18 22:43 ` Stefan Monnier
2011-02-22 21:51 ` Ted Zlatanov [this message]
2011-02-18 23:04 ` Lars Ingebrigtsen
2011-02-22 22:46 ` Stefan Monnier
2011-02-16 21:26 ` Lars Magne Ingebrigtsen
[not found] <jwv8vxg7nt4.fsf-monnier+@gnu.org>
[not found] ` <mailman.0.1298509609.2066.bug-gnu-emacs@gnu.org>
2011-02-24 12:50 ` Ted Zlatanov
2011-02-24 15:22 ` Stefan Monnier
2011-02-24 16:29 ` Ted Zlatanov
2011-02-25 4:29 ` Lars Magne Ingebrigtsen
2011-02-25 11:21 ` Ted Zlatanov
2011-02-25 11:50 ` Ted Zlatanov
2011-03-05 12:17 ` Lars Magne Ingebrigtsen
[not found] ` <mailman.17.1299357452.24947.bug-gnu-emacs@gnu.org>
[not found] ` <874o7e23i8.fsf@lifelogs.com>
[not found] ` <mailman.2.1299548219.4111.bug-gnu-emacs@gnu.org>
[not found] ` <87lj0ptv9y.fsf@lifelogs.com>
2011-03-08 19:49 ` 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=87lj17ybz2.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=bug-gnu-emacs@gnu.org \
--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).