From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Simon Josefsson <jas@extundo.com>, ding@gnus.org
Subject: Re: No Gnus todo item
Date: Thu, 08 May 2003 13:14:03 -0400 [thread overview]
Message-ID: <4nn0hxbbtw.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ruoof2djtor.fsf@billw2lx.wolfram.com> (Bill White's message of "Thu, 08 May 2003 11:21:08 -0500")
On Thu, 08 May 2003, billw@wolfram.com wrote:
> On Thu May 08 2003 at 06:07, Simon Josefsson <jas@extundo.com> 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. 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?
Thanks
Ted
next prev parent reply other threads:[~2003-05-08 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 11:07 Simon Josefsson
2003-05-08 12:03 ` Reiner Steib
2003-05-08 13:26 ` Simon Josefsson
2003-05-08 16:24 ` Bill White
2003-05-09 7:08 ` Kai Großjohann
2003-05-13 18:02 ` Lars Magne Ingebrigtsen
2003-05-08 16:21 ` Bill White
2003-05-08 17:14 ` Ted Zlatanov [this message]
2003-05-08 17:29 ` Simon Josefsson
2003-05-08 18:56 ` Ted Zlatanov
2003-05-08 22:48 ` Simon Josefsson
2003-05-09 16:32 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4nn0hxbbtw.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=jas@extundo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).