From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36580 Path: main.gmane.org!not-for-mail From: Nevin Kapur Newsgroups: gmane.emacs.gnus.general Subject: Re: Imap Problem Date: 05 Jun 2001 10:58:55 -0400 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 1035172141 9299 80.91.224.250 (21 Oct 2002 03:49:01 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:49:01 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 5432 invoked from network); 5 Jun 2001 15:01:33 -0000 Original-Received: from fermat.mts.jhu.edu (root@128.220.17.18) by gnus.org with SMTP; 5 Jun 2001 15:01:33 -0000 Original-Received: (from kapur@localhost) by fermat.mts.jhu.edu (8.11.2/8.11.2) id f55Ewv818327; Tue, 5 Jun 2001 10:58:57 -0400 X-Authentication-Warning: fermat.mts.jhu.edu: kapur set sender to nevin@jhu.edu using -f Original-To: ding@gnus.org X-Face: 5qz+Fg"Lb1Z3i<6h&9Ax$jfq]k{-f:z_Uk_fQ_DOy|7;xWm4@bDK52s/-A\!8g'3a}peKv> u;mMlqf!3"K"X5B;2E|Nz}< (Mats Lidell's message of "Tue, 05 Jun 2001 10:34:47 +0200") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Academic Rigor) Original-Lines: 19 Xref: main.gmane.org gmane.emacs.gnus.general:36580 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36580 Mats Lidell writes: > Could someone please explain how setting the buffer when looking for > the imap response could possibly affect how passwords are read from > the minibuffer? FWIW, I see the same problem when prompted for to enter my GPG passphrase. I don't use IMAP. When this happens (like right now), I can reproduce the problem by evaluating (read-passwd "Pass:") in the *scratch* buffer, but I can't reproduce the situation that brings it about. I brought this up on the ding list and comp.emacs.xemacs but didn't get any solutions. I suspect this is an XEmacs 21.4.x bug. -- Nevin