From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36587 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: Imap Problem Date: 05 Jun 2001 20:19:32 +0200 Message-ID: References: <76y9rdaxai.fsf@newjersey.ppllc.com> <76zobsxrkj.fsf@newjersey.ppllc.com> <76n17o9q1k.fsf@newjersey.ppllc.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035172147 9349 80.91.224.250 (21 Oct 2002 03:49:07 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:49:07 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 7907 invoked from network); 5 Jun 2001 18:18:42 -0000 Original-Received: from dolk.extundo.com (195.42.214.242) by gnus.org with SMTP; 5 Jun 2001 18:18:42 -0000 Original-Received: from barbar.josefsson.org (slipsten.extundo.com [195.42.214.241]) (authenticated) by dolk.extundo.com (8.11.3/8.11.3) with ESMTP id f55IImq29958; Tue, 5 Jun 2001 20:18:49 +0200 Original-To: Jake Colman In-Reply-To: <76n17o9q1k.fsf@newjersey.ppllc.com> (Jake Colman's message of "04 Jun 2001 12:18:47 -0400") Mail-Copies-To: nobody User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Academic Rigor) Original-Lines: 16 Xref: main.gmane.org gmane.emacs.gnus.general:36587 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36587 Jake Colman writes: > I went back to my prior version of pgnus, prior to Simon's commits, and > manually applied on my Matt's one line change to imap.el. With this patch > applied, I cannot start gnus in its own frame. if I do, the password > prompting is messed up and it eats my CR instead of processing the password. > So this problem is specifically related to Matt's portion of the patch and > was not caused by whatever else Simon patched. Does the problem also disappear if you remove the patch? (Just to single out any other factors.) I suspect something else is wrong, maybe a `read-passwd' bug, since the password has always been read from within the process buffer, and adding an extra `set-buffer' to change to that buffer shouldn't harm anything. (Famous last words.)