From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: bug#8050: Gnus does not connect to my IMAP server any more
Date: Tue, 8 Mar 2011 13:49:29 -0600 [thread overview]
Message-ID: <87oc5ls88m.fsf@lifelogs.com> (raw)
In-Reply-To: <87lj0ptv9y.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 08 Mar 2011 10:46:33 -0600")
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.bug as well.
On Tue, 08 Mar 2011 10:46:33 -0600 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Mon, 07 Mar 2011 18:10:38 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
SM> - Also when I'm then asked for a password, the prompt says "Password for
SM> user foo, host bar" which is more verbose but not more clear than
SM> "Password for foo@bar" used in earlier Gnus.
>>> That's the default prompt. Every package can supply their own which
>>> makes sense in context. So nnimap.el could supply the password prompt
>>> "IMAP password for user %u, host %h:%p" for instance. Does that seem OK
>>> to you? If so I can add it to nnimap.el.
SM> I mostly care about nnimap for now because it's the only case I bumped
SM> into, but I can't imagine why it would be better to use "user foo, host
SM> bar" for the default, since all uses I can think of will want to
SM> override it with the "foo@bar" syntax instead.
TZ> This is the current default prompt list:
TZ> (prompt (or (aget auth-source-creation-prompts r)
TZ> (case r
TZ> ('secret "%p password for user %u, host %h: ")
TZ> ('user "%p user name: ")
TZ> ('host "%p host name for user %u: ")
TZ> ('port "%p port for user %u and host %h: "))
TZ> (format "Enter %s (%%u@%%h:%%p): " r)))
TZ> Can you please propose specific replacements?
I added specific prompts for nnimap.el:
(let* ((auth-source-creation-prompts
'((user . "IMAP user at %h: ")
(secret . "IMAP password for %u@%h: ")))
...
which should look OK. But if you or anyone else can suggest default
prompts, that would be great.
Ted
next prev parent reply other threads:[~2011-03-08 19:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
2011-02-18 23:04 ` Lars Ingebrigtsen
2011-02-22 22:46 ` Stefan Monnier
2011-02-16 21:26 ` Lars Magne 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=87oc5ls88m.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).