Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: `^ ... RET' server mode adds groups to *Group*?
Date: 29 Jan 2001 10:22:23 -0800	[thread overview]
Message-ID: <m3snm2ql04.fsf@reader.newsguy.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:

> Karl Kleinpaste <karl@charcoal.com> writes:
> 
> [...]
> 
> > I think having this variable defaulting to t is suboptimal.  And it's
> > much, much slower (due to having to go through the gyrations of adding
> > groups to *Group*) than browsing a server in its own server buffer.
> 
> The advantage is that you can access groups in group buffer, but you
> cannot in server browse buffer.


Have things already been changed?  Todays cvs shows different
behavior.

`^' in `server' buffer and <RET> on nntp server, immediately moves me to
group buffer displaying all groups I have, including unsubscribed ones
under that server.

I don't see the massive work Karl describes.  What I see is nothing
more than `L' listing but limited to nntp server groups.

A <spc> on nntp server seems to give the old behavior in tact.

What is the intent, again?




  parent reply	other threads:[~2001-01-29 18:22 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
2001-01-29 18:22         ` Harry Putnam [this message]
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=m3snm2ql04.fsf@reader.newsguy.com \
    --to=reader@newsguy.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).