From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.bugs Subject: Re: bug#8050: Gnus does not connect to my IMAP server any more Date: Tue, 08 Mar 2011 12:33:33 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87d3m1tqbm.fsf@lifelogs.com> References: <874o7e23i8.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1299609614 10876 80.91.229.12 (8 Mar 2011 18:40:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2011 18:40:14 +0000 (UTC) To: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 08 19:40:10 2011 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Px1pJ-000715-LE for geb-bug-gnu-emacs@m.gmane.org; Tue, 08 Mar 2011 19:40:09 +0100 Original-Received: from localhost ([127.0.0.1]:37142 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Px1pJ-0006Wa-5Q for geb-bug-gnu-emacs@m.gmane.org; Tue, 08 Mar 2011 13:40:09 -0500 Original-Path: usenet.stanford.edu!news-transit.tcx.org.uk!news.albasani.net!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.bug Original-Lines: 42 Original-X-Trace: news.albasani.net TFXjZ1rGMKF4fjxBupTtwOPGaATJeTB3Uc/BIsRRBMlw07wnwOhFauthrBoNNPJfIgaCH1l4s7+chUiatsn5Yw== Original-NNTP-Posting-Date: Tue, 8 Mar 2011 18:33:33 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="my1W/K6Lw5H9nq9vkYl6q/gb5ETEPcbMUwEbAkpMrSE9E2wyIJNvoTpLSicuMxmVe/Ry2ZDPP3dc7EQbNEkx0R07HMfJO/MtkzVr2A8yYNg7B+V62a1IpKaO8dvqzp61"; mail-complaints-to="abuse@albasani.net" User-Agent: Gnus/5.110014 (No Gnus v0.14) Emacs/24.0.50 (gnu/linux) X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Cancel-Lock: sha1:o2LdG3hHPl0yLcECwTM7wjEs+mA= sha1:I7MBSwP9qk7NltT/QhkoTpHCkHI= Original-Xref: usenet.stanford.edu gnu.emacs.bug:72097 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:44793 Archived-At: On Mon, 07 Mar 2011 12:23:59 -0600 Ted Zlatanov wrote: TZ> On Sat, 05 Mar 2011 15:13:53 -0500 Stefan Monnier wrote: SM> - But when I'm asked for a user name there is no default, whereas earlier SM> my local user name was used as default (which happens to work for me on SM> most of the machines to which I can connect). Please use the local user SM> name as default in that prompt. TZ> I'll add that. I thought I did but must have forgotten. This is done. SM> - I'm asked whether to save the password regardless of whether the SM> password and user names are correct or not. That's really bad. TZ> auth-source.el doesn't know at that time whether the authentication will TZ> be successful. I think you're saying we need an `auth-source-save' TZ> function to be called after the fact instead of a ":create t" parameter. I added this as part of the auth result. So you can say (example from nnimap.el, where the 3rd element of the credentials is the :save-function property of the search result): (when (functionp (nth 2 credentials)) (funcall (nth 2 credentials))) after a successful login. This means that everyone using the ":create t" parameter will have to adjust for the :save-function. Currently that's just nnimap.el and sieve-manage.el (which I'll modify when you and Lars agree this is the right approach). SM> - After refusing to save the password in authinfo.gpg, I get a message SM> along the lines of "auth-source-search: CREATED 1 results ...". SM> I don't care whether "results" is replaced by "result" when there's SM> only 1, but this looks like a debug message which should disappear. OK, it's gone. But we show a shorter one with `message' unconditionally, which I think is the right thing to do. Ted