From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/52443 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: No Gnus todo item Date: Thu, 08 May 2003 19:29:25 +0200 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <4nn0hxbbtw.fsf@lockgroove.bwh.harvard.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1052414929 6527 80.91.224.249 (8 May 2003 17:28:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 8 May 2003 17:28:49 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M987@lists.math.uh.edu Thu May 08 19:28:47 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19DpBt-0001fq-00 for ; Thu, 08 May 2003 19:28:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19DpD6-0000u8-00; Thu, 08 May 2003 12:29:36 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19DpD2-0000u3-00 for ding@lists.math.uh.edu; Thu, 08 May 2003 12:29:32 -0500 Original-Received: (qmail 54633 invoked by alias); 8 May 2003 17:29:31 -0000 Original-Received: (qmail 54628 invoked from network); 8 May 2003 17:29:31 -0000 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net (HELO yxa.extundo.com) (217.13.230.178) by sclp3.sclp.com with SMTP; 8 May 2003 17:29:31 -0000 Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h48HTPB4024836 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Thu, 8 May 2003 19:29:26 +0200 Original-To: Bill White Mail-Copies-To: nobody X-Payment: hashcash 1.2 0:030508:billw@wolfram.com:255c9080d8cf1840 X-Hashcash: 0:030508:billw@wolfram.com:255c9080d8cf1840 X-Payment: hashcash 1.2 0:030508:ding@gnus.org:94e10c92b9852e75 X-Hashcash: 0:030508:ding@gnus.org:94e10c92b9852e75 In-Reply-To: <4nn0hxbbtw.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 08 May 2003 13:14:03 -0400") User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3.50 (gnu/linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:52443 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:52443 Ted Zlatanov writes: > On Thu, 08 May 2003, billw@wolfram.com wrote: >> On Thu May 08 2003 at 06:07, Simon Josefsson said: >> >>> Pressing M-x gnus RET should load gnus, load .newsrc.eld etc, and >>> display the group buffer. This shouldn't take longer than 5s. >>> This is in line with the GUI design criteria "minimize time the >>> user can't access the user interface". >>> >>> Fetching new mail, and updating the article counts should be done >>> after pressing 'g'. >> >> That's an excellent idea! Occasionally, I get into a situation >> where I need to load without downloading because I've screwed >> something up, so I have to edit mail-sources temporarily to keep new >> mail out of the mess. > > But that's confusing to new users, every MUA I have used will load new > mail at startup. Before displaying the user interface? Most MUAs I recall using (Mozilla, Evolution, Kmail, Outlook, Pine) display the GUI immediately and then some of them (exceptions are Pine and Outlook, as far as I can recall) will continue to update the message counts in the background. > May I suggest either a variable like gnus-startup-without-scan or a > function gnus-fast? The function seems the better solution. You > startup gnus with emacs -f gnus-fast and then `g' is still bound to > the gnus function so things work like they always have. > > In fact, it seems like the gnus function already has a dont-connect > parameter. Is that not useful? It is, and it may be tested by using M-x gnus-no-server RET or M-x gnus-unplugged RET depending on preference. I'm talking about the default behavior. Perhaps the idea doesn't make sense unless the asynchronous update of read counts is implemented. If so, the consider that implemented too, when thinking about the feature.