From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: bug-gnu-emacs@gnu.org, ding@gnus.org
Subject: Re: bug#8050: Gnus does not connect to my IMAP server any more
Date: Fri, 18 Feb 2011 17:43:13 -0500 [thread overview]
Message-ID: <jwvd3mpq8fq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874o81xfng.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 18 Feb 2011 14:16:03 -0600")
>>> - then I get prompted to save the password, which is the worst of the
>>> three:
LI> Yes, it should just say "Save the password for future sessions? " and
LI> not much more.
> How about:
> "Save the $HOSTNAME password for future sessions? y/n/s/?"
The previous prompt included the ~/.authinfo.gpg file name which
I thought was good. On the contrary, the hostname info seems redundant
since it's already been displayed by the previous 2 prompts.
> where `s' shows the line we will add with the password replaced by ****?
Here are some ways to handle the "showing the line":
1- show it in the prompt: loud, noisy, and worst of all, shows the
password in the clear, right after you entered it via `read-passwd'
which was careful to keep it hidden.
2- Add an `s' option to the prompt.
3- Add a second prompt (when if the user selected `y') to confirm the
actual text that will be saved. Can be kind of a pain for the user,
but presumably, password aren't saved all the time.
4- not show it at all, let the user visit the file afterwards to see
what happened if he wants to.
1 is out. 2 seems like a lot of trouble compared to using y-or-n-p
(tho, if you add an `N' option anyway to remember not to prompt next
time, the extra work is already done). 3 might be a bit annoying to
some of the users (especially those who want to save the password but
don't want to have it displayed). 4 seemed sufficient to me, but
apparently YMMV.
So yes, I'd vote for 2 or 4 (as the coder, I'd choose 4 ;-)
Stefan
next prev parent reply other threads:[~2011-02-18 22:43 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 [this message]
2011-02-22 21:51 ` Ted Zlatanov
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=jwvd3mpq8fq.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bug-gnu-emacs@gnu.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).