From: nyc4bos@aol.com
To: ding@gnus.org
Subject: Re: auth-source problem
Date: Sun, 13 Mar 2011 00:28:20 -0500 [thread overview]
Message-ID: <84k4g3oah7.fsf@aol.com> (raw)
In-Reply-To: <87sjus9pmp.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sat, 12 Mar 2011 00:47:31 -0500 nyc4bos@aol.com wrote:
>
> n> Unable to open server nnimap+aol due to: Invalid function: 993
>
> n> auth-source.el doesn't show up (not prompting) for AOL at all and
> n> I do NOT have it in my ~/.authinfo.gpg file so I think at least
> n> this problem is related to auth-source.el
>
> You were right and I finally found the problem. nnimap.el traps the
> error so you don't know it came from auth-source.el (actually from
> `replace-regexp-in-string' which tries to evaluate non-string
> arguments). I believe it's fixed now.
Yes, it's fixed now with the patch in git that I obtained.
Thanks for hunting this bug down!
One issue I still have though:
The prompt says:
IMAP user at imap.gmail.com:
I think that the prompt should have the default user showing.
Before, you were able to specify in your gnus-(secondary)-select-methods:
...
(nnimap "aol"
(nnimap-address "imap.aim.com")
(nnimap-server-port 993)
(nnimap-stream ssl)
(imap-default-user "nyc4bos"))
This was when nnimap used imap.el but I think a `nnimap-username' should
be defined (`nil' as the default, meaning use '(user-login-name)' as per
auth-source.el if found in authinfo(.gpg), netrc, or `nnimap-username'
is not set).
I believe it was Katsumi Yamaoka that provided such a patch to
nnimap.el using:
(defvoo nnimap-username nil
"The IMAP username used to login.")
(defun nnimap-credentials (address ports &optional username)
...
In any event, I think that `(user-login-name)' should at least
show up in the prompt if not `nnimap-username'.
(Yes, I realize that it will use `(user-login-name)' if you just
hit RET at the prompt even if it doesn't originally show it.
I think you also rseponded to Stefan in bug#8050 that you fixed
this (showing the default user) but I can't seem to find that patch
in either git or bzr as of yet).
Thanks.
next prev parent reply other threads:[~2011-03-13 5:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 2:55 nyc4bos
2011-03-07 11:09 ` Ted Zlatanov
2011-03-09 2:40 ` nyc4bos
2011-03-09 15:24 ` Ted Zlatanov
2011-03-10 4:53 ` nyc4bos
2011-03-10 15:54 ` Ted Zlatanov
2011-03-12 5:47 ` nyc4bos
2011-03-12 18:10 ` Ted Zlatanov
2011-03-13 5:28 ` nyc4bos [this message]
2011-03-13 14:05 ` Ted Zlatanov
2011-03-17 3:27 ` nyc4bos
2011-03-17 11:04 ` Ted Zlatanov
2011-03-17 16:50 ` Lars Magne Ingebrigtsen
2011-03-17 18:16 ` Andreas Schwab
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=84k4g3oah7.fsf@aol.com \
--to=nyc4bos@aol.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).