Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: `^ ... RET' server mode adds groups to *Group*?
Date: 29 Jan 2001 08:52:33 -0500	[thread overview]
Message-ID: <2nr91mmpni.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <vxkzogbi7wo.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "28 Jan 2001 18:17:11 -0500")

Karl Kleinpaste <karl@charcoal.com> writes:

> Go into the server buffer with `^'.
> Wander down to an appropriate NNTP server, e.g. my primary, as
> {nntp:news} (opened)
> Now RET.
> 
> XEmacs cogitates at great length, presumably sorting the group list.
> At the end of this effort, I am placed in my *Group* buffer, with
> _all_ my server's groups added to *Group* at level 9 "killed" status.

It is an experimental feature in oGnus.  Only unknown or killed groups
are listed at level 9, and others groups are listed at the end of the
buffer if you use topic mode.  You may type `^ SPC' to list groups in
the old way, or (setq gnus-server-browse-in-group-buffer nil) to
disable the feature.

> Doubleplusungood.  I thought `^ RET' should give me a server-specific
> group listing for transient or ephemeral access to groups?

You can access killed groups. At least, I did it.

ShengHuo

-- 
(setq gnus-posting-styles '((".*" (signature-file "~/.signature"))))



      parent reply	other threads:[~2001-01-29 13:52 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
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 [this message]

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=2nr91mmpni.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).