🚀 go-pugleaf

I'm currently "testdriving" GNUS, and have a couple of questions I
wonder if you could help me with (I curently use Gnews).

In some sort of semblance of decreasing importance:

1) I guess a Sun 3/180 must be a "slow" machine, since I had to set
gnus-group-headers to nil in gnus-Exit-group-hook. Without this
leaving some newsgroups was just too painful. This is pretty much OK,
except I'd like to nuke the xrefs of the articles I actually read. I
expect I need some tiny little incantation in
gnus-Article-prepare-hook. Can anyone tell me what that would be
(bonus marks if the xrefs get nuked after the first page is displayed :-)
Out of curiousity, how fast a machine do you need to have before
leaving a newsgroup isn't noticeable? (Sometimes I think GNUS and
Gnews should talk to rn or rrn instead of nntp. Sigh).

2) I often read news from home at 2400 baud, and I'd like to make gnus
only display articles when I explicitly ask for them (i.e. hit the
spacebar). Although I have auto-select-first set to nil, when I, for
example, kill the current subject, after the kills are done the first
remaining article is brought up. (Hope that's clear).

3) How can I go to the next newsgroup in subject mode rather than back
to the newsgroups buffer when I catch-up within a subject buffer.

4) I am probably an idiot. My attempts to automatically sort subjects
(by subject) in gnus-Subject-mode-hook has failed dismally.

5) We have both  nntp running and news on local spool. I am assuming
that the local spool code is faster, except for possibly following
article references back. Is this right?

Anyway, thanks in advance for any insight or advice you can give me.

--
	  Brian Glendenning - Radio astronomy, University of Toronto
brian@radio.astro.utoronto.ca uunet!utai!radio!brian  glendenn@utorphys.bitnet