From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/35573 Path: main.gmane.org!not-for-mail From: "Bjørn Mork" Newsgroups: gmane.emacs.gnus.general Subject: Re: Timeouts with nnimap? Date: 02 Apr 2001 12:25:16 +0200 Organization: DoD Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035171297 3845 80.91.224.250 (21 Oct 2002 03:34:57 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:34:57 +0000 (UTC) Return-Path: Original-Received: (qmail 28259 invoked by alias); 2 Apr 2001 10:25:18 -0000 Original-Received: (qmail 28254 invoked from network); 2 Apr 2001 10:25:18 -0000 Original-Received: from quimby.gnus.org (195.204.10.139) by gnus.org with SMTP; 2 Apr 2001 10:25:18 -0000 Original-Received: (from news@localhost) by quimby.gnus.org (8.9.3/8.9.3) id MAA32146 for ding@gnus.org; Mon, 2 Apr 2001 12:25:14 +0200 (CEST) Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-NNTP-Posting-Host: 148.122.193.186.dhcp.nextra.no Original-X-Trace: quimby.gnus.org 986207113 20706 148.122.193.186 (2 Apr 2001 10:25:13 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 2 Apr 2001 10:25:13 GMT User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.7 Original-Lines: 26 Xref: main.gmane.org gmane.emacs.gnus.general:35573 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:35573 Simon Josefsson writes: > Steinar Bang writes: > > > nnimap server up and running, and let Gnus stay connected long enough > > for the network to go flaky on you. > > > > You also get it, as Bjørn pointed out, if you suspend a laptop without > > unplugging Gnus, and then resuming it in a different network. > > > > `C-x C-c' and starting a new emacs, is then the only option. > > You can delete the " *nnimap* yourserver*" buffer too. Ah, now *that's* intuitive ;-) > Maybe we could add a backend function `nnfoo-force-close-server'? > That could be called if you do C-u C in the server buffer? Or perhaps > `nnimap-close-server' simply shouldn't try to be nice to server, and > just kill the buffer after 5s or something. I would prefer the latter. Preferably with a warning to allow people to fix their network connection in case the error is caused by an unintentional disconnect. Bjørn