From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: `^ ... RET' server mode adds groups to *Group*?
Date: 29 Jan 2001 20:12:42 -0800 [thread overview]
Message-ID: <m37l3dpxv5.fsf@reader.newsguy.com> (raw)
In-Reply-To: <5bu26ioyx0.fsf@avocet.cs.rochester.edu> (ShengHuo ZHU's message of "29 Jan 2001 16:01:47 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > I'm still confused as to what it does. Is it different than pressing
> > `A A' in group buffer?
>
> There differences are that `A A'
> 1. does not list groups on foreign servers;
> 2. sorts groups by name and list them in flat mode;
> 3. does not show the levels of groups.
>
> > That server has some 29,000+ groups.
> >
> > Pressing `A A' in Group gives me.
> > some 29,000 lines 1300K of active file
> >
> > Pressing <RET> on that nntp server in server_buffer gives me some 40 lines
>
> Do you use it in unplugged mode?
Ahhh theres the rub... I was unplugged. I see how it works now and
the extra functionality is nice. Esp. since we still have <spc> for
the old behavior.
Regexp matching is another good reason to move it to group buffer.
[...]
> > So it is different than `A A'?
>
> Yes.
Yes indeed. Another difference that isn't so apparent is that `A A'
works the same plugged or unplugged. (long as a link is up, of course)
Whereas the new `<RET> on server' offers different functionality
plugged and unplugged. More options, always a plus.
One thing I noticed that may be a small bug is that under certain
conditions after pressing <spc> on a server. When leaving that buffer
with `q'. It can cause a major cpu drain while emacs pulls down all
available cpu and does nothing (not visibly any way).
I haven't been able to repoduce this reliably but it happened three
times (not in sequence) while I've been experimenting with this new
functionality.
next prev parent reply other threads:[~2001-01-30 4:12 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 [this message]
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=m37l3dpxv5.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.org \
/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).