Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!giza.cis.ohio-state.edu!karl From: karl@giza.cis.ohio-state.edu (Karl Kleinpaste) Newsgroups: gnu.emacs.gnus Subject: Re: Novice GNUS questions Message-ID: Date: 25 May 89 11:56:21 GMT References: <8905250557.AA24607@radio.astro.utoronto.ca> Sender: news@tut.cis.ohio-state.edu Distribution: gnu Organization: Ohio State Computer Science In-reply-to: brian@RADIO.ASTRO.UTORONTO.CA's message of 25 May 89 05:57:39 GMT Lines: 48 brian@RADIO.ASTRO.UTORONTO.CA (Brian Glendenning) writes: 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. Hm - I use a Sun3/50 with an NFS-mounted /usr/spool/news most of the time, and I seldom have any problem. When there are a *lot* of articles in the newsgroup, exit may take a while, but that's relatively infrequent. Can you provide examples? How many articles, how much Xref: resolution, etc, make it seem slow? 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). `k' is gnus-Subject-kill-same-subject-and-select. If instead you use `C-k,' then you execute gnus-Subject-kill-same-subject, which does not select the next article. 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. You can't, from what I've been able to determine. 4) I am probably an idiot. My attempts to automatically sort subjects (by subject) in gnus-Subject-mode-hook has failed dismally. You're not an idiot, you just haven't read the documentation sufficiently carefully. You're using the wrong hook. From the Info system node `Hooks': This hook is intended to customize Subject Mode only once. You should instead be using gnus-Select-group-hook, which is run each time that any group is selected. There is a good example there (in `Hooks,' that is) of how to do what you want. 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? I think so, but my usage of the NNTP code has been only slight, for testing purposes - we normally don't allow NNTP reading, depending on an NFS-mounted spool instead. --Karl