From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36543 Path: main.gmane.org!not-for-mail From: Jake Colman Newsgroups: gmane.emacs.gnus.general Subject: Re: Imap Problem Date: 01 Jun 2001 09:22:52 -0400 Sender: colman@ppllc.com Message-ID: <76zobsxrkj.fsf@newjersey.ppllc.com> References: <76y9rdaxai.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 1035172110 9146 80.91.224.250 (21 Oct 2002 03:48:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:48:30 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 21125 invoked from network); 1 Jun 2001 13:23:52 -0000 Original-Received: from unknown (HELO newjersey.ppllc.com) (209.208.206.221) by gnus.org with SMTP; 1 Jun 2001 13:23:52 -0000 Original-Received: (from colman@localhost) by newjersey.ppllc.com (8.9.3/8.9.3) id JAA15389; Fri, 1 Jun 2001 09:22:53 -0400 (EDT) X-Authentication-Warning: newjersey.ppllc.com: colman set sender to colman@ppllc.com using -f Original-To: Mats Lidell X-Attribution: Jake X-URL: http://www.ppllc.com In-Reply-To: (Mats Lidell's message of "01 Jun 2001 09:00:09 +0200") User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.4 (Academic Rigor) Original-Lines: 42 Xref: main.gmane.org gmane.emacs.gnus.general:36543 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36543 >>>>> "ML" == Mats Lidell writes: ML> Yes! You are not alone ;-) No! No solution ;-( Great! Misery just loves company... ML> There might be more situations that can lead to this behavior. Such ML> as the imap connection timing out. What I have found useful is to ML> quite often check for new mail and by that avoid the timeout. Yes, that's exactly what I do. Unfortunately, if you don't do it quite often enough you're screwed and have to restart your entire XEmacs session. ML> By looking at the nnimap code I can't however figure out how this can ML> ever happen and obviously the code does work for a lot so it is a ML> really hard bug to find. I guess someone who gets this problem must ML> look into it ;-) OK. Someday ... There are enough of use with this problem that you'd think someone, somewhere would try to run it down. I'd try to look into but I have no idea where to begin. In case this helps, since upgrading to 21.4.3 and the latest packages, I can make this happen consistently if I just do the following: 1) Start XEmacs. 2) C-x f .emacs 2) C-x 5 b 3) M-x gnus in the new frame The only way I can successfully start gnus is if I start gnus from the initial frame and create my additional frames only after gnus is up and running. -- Jake Colman Principia Partners LLC Phone: (201) 946-0300 Harborside Financial Center Fax: (201) 946-0320 902 Plaza II Beeper: (800) 928-4640 Jersey City, NJ 07311 E-mail: colman@ppllc.com E-mail: jcolman@jnc.com web: http://www.ppllc.com