From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: `^ ... RET' server mode adds groups to *Group*?
Date: 29 Jan 2001 09:58:09 -0500 [thread overview]
Message-ID: <vxkitmyiewu.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <2nlmrump3k.fsf@tiger.jia.vnet> (ShengHuo ZHU's message of "29 Jan 2001 09:04:31 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> The advantage is that you can access groups in group buffer, but you
> cannot in server browse buffer.
I don't understand why it's an advantage.
Having a server-browsing buffer is for the specific purpose of looking
over what a particular server has to offer, and allowing the user to
ephemerally look into any of them, or do a general subscription pick
out of the complete list.
How does tacking this monstrous mass of mostly crud into *Group* do
anything useful for me? On my PII-450, it took well over 2 minutes of
internal hackery for Gnus to do the shovel-groups-into-*Group*-as-
killed (because managing *Group* is comparatively convoluted), whereas
going for the original buffer-browsing-server-by-itself popped up in
all of perhaps 15 seconds. My active file is about 600K.
I just don't see what new capability this is supposed to provide.
next prev parent reply other threads:[~2001-01-29 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 23:17 Karl Kleinpaste
2001-01-29 3:14 ` Bill White
2001-01-29 7:47 ` Harry Putnam
2001-01-29 13:50 ` Karl Kleinpaste
2001-01-29 14:04 ` ShengHuo ZHU
2001-01-29 14:58 ` Karl Kleinpaste [this message]
2001-01-29 18:22 ` Harry Putnam
2001-01-29 19:08 ` ShengHuo ZHU
2001-01-29 20:16 ` Harry Putnam
2001-01-29 21:01 ` ShengHuo ZHU
2001-01-30 4:12 ` Harry Putnam
2001-01-30 4:25 ` ShengHuo ZHU
2001-01-29 13:52 ` ShengHuo ZHU
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=vxkitmyiewu.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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).