From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Making Gnus ask my IMAP username and password after the recent auth-source changes
Date: Wed, 23 Feb 2011 08:47:11 -0600 [thread overview]
Message-ID: <871v2yq040.fsf@lifelogs.com> (raw)
In-Reply-To: <87d3mj3zfs.fsf@gnus.org>
On Wed, 23 Feb 2011 00:52:39 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> This is now the case. Any parameters with a nil or t value will be
>> omitted from the saved line. The password is the only one we will ask
>> for.
LI> It needs to ask for the user name, too, doesn't it?
Maybe. Right now it's guessed. People seem to prefer fewer prompts and
you can always `e'dit the line afterwards. I mentioned that in my reply
to Simon Josefsson just now, too.
LI> With this call:
LI> (nnimap-credentials "foo" '("imap" "imaps"))
LI> I get this prompt, which is still confusing (in addition to not
LI> prompting for the user name):
LI> Password for [any user]@foo:(imap, imaps)?
LI> It should say
LI> "imap user name at foo: "
LI> and
LI> "imap password for larsi at foo: "
It should have said "Password for [any user]@foo:imap?" and I guess
that's a bug (fix just went in) . The "any user" and "any port" part is
necessary IMO to make the intent clear.
If the port is numeric your proposal is not so good:
"143 password at foo: "
so I'd rather keep the current prompt.
LI> In addition, the prompt you get afterwords is still way to complicated.
LI> nnimap has decided what port number to put into the line, so offering to
LI> edit the line at all is just confusing. If the user wants to edit the
LI> stuff, the user knows that they can just edit the ~/.authinfo file
LI> themselves.
I disagree. You can make it an option to bypass that prompt if you
like, but I really want to show it by default. It's a rare event and
when it happens, the user should know it's going to modify a netrc file.
The user doesn't necessarily know to edit the .authinfo file. He may
not even know what that is.
Ted
next prev parent reply other threads:[~2011-02-23 14:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 2:06 Raphael Kubo da Costa
2011-02-15 13:46 ` Ted Zlatanov
2011-02-15 20:57 ` Raphael Kubo da Costa
2011-02-16 19:13 ` Ted Zlatanov
2011-02-16 20:39 ` Matt Lundin
2011-02-16 20:46 ` Ted Zlatanov
2011-02-17 1:15 ` Matt Lundin
2011-02-17 11:03 ` Ted Zlatanov
2011-02-17 13:49 ` Matt Lundin
2011-02-17 14:20 ` Matt Lundin
2011-02-17 15:22 ` Steinar Bang
2011-02-18 20:21 ` Ted Zlatanov
2011-02-21 19:40 ` Steinar Bang
2011-02-17 3:34 ` Raphael Kubo da Costa
2011-02-17 11:44 ` Ted Zlatanov
2011-02-17 13:34 ` Raphael Kubo da Costa
2011-02-17 14:16 ` Ted Zlatanov
2011-02-17 23:54 ` Lars Ingebrigtsen
2011-02-18 20:19 ` Ted Zlatanov
2011-02-18 23:10 ` Lars Ingebrigtsen
2011-02-22 21:52 ` Ted Zlatanov
2011-02-23 8:52 ` Lars Ingebrigtsen
2011-02-23 14:47 ` Ted Zlatanov [this message]
2011-02-23 17:00 ` Raphael Kubo da Costa
2011-02-23 17:09 ` Ted Zlatanov
2011-02-23 17:56 ` Raphael Kubo da Costa
2011-02-23 18:56 ` Ted Zlatanov
2011-02-25 4:42 ` Lars Ingebrigtsen
2011-02-25 11:31 ` Ted Zlatanov
2011-03-05 12:15 ` Lars Magne Ingebrigtsen
2011-03-08 18:26 ` Ted Zlatanov
2011-03-15 16:28 ` Lars Magne Ingebrigtsen
2011-03-15 16:43 ` Ted Zlatanov
2011-02-23 23:35 ` Lars Ingebrigtsen
2011-02-23 23:36 ` Lars Ingebrigtsen
2011-02-24 5:43 ` Ted Zlatanov
2011-02-24 11:35 ` Lars Ingebrigtsen
2011-02-24 13:06 ` Ted Zlatanov
2011-02-24 13:48 ` Raphael Kubo da Costa
2011-02-24 16:42 ` Ted Zlatanov
2011-02-25 4:47 ` 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=871v2yq040.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).