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: 28 Jan 2001 23:47:42 -0800	[thread overview]
Message-ID: <m3r91mby01.fsf@reader.newsguy.com> (raw)
In-Reply-To: Bill White's message of "28 Jan 2001 21:14:35 -0600"

Bill White <billw@wolfram.com> writes:

> On Sun Jan 28 2001 at 17:17, Karl Kleinpaste <karl@charcoal.com> said:
> 
>     kk> Go into the server buffer with `^'.  Wander down to an
>     kk> appropriate NNTP server, e.g. my primary, as {nntp:news}
>     kk> (opened) Now RET.
> 
>     kk> XEmacs cogitates at great length, presumably sorting the group
>     kk> list.  At the end of this effort, I am placed in my *Group*
>     kk> buffer, with _all_ my server's groups added to *Group* at
>     kk> level 9 "killed" status.
> 
> Same here with GNU Emacs 21.0.95.1 (i586-pc-linux-gnu, X toolkit) of
> 2001-01-10 on g.wolfram.com.  Didn't that start happening with ognus?


Still having an older version of 5.8.8 available I see no such delay
but an immediate listing for...I guess what Karl calls:
"transient or ephemeral access"

It shows the same groups that `L' would show only limited to that
server, and in a buffer called "*Gnus Browse Server*", all at killed
status. 



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

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=m3r91mby01.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).