Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!nosc!ucsd!rutgers!mailrus!cornell!batcomputer!itsgw!rpi!pawl.rpi.edu!tale From: tale@pawl.rpi.edu (David C Lawrence) Newsgroups: comp.emacs Subject: GNUS Message-ID: Date: 21 Jan 89 03:21:18 GMT Sender: usenet@rpi.edu Organization: The Octagon Room Lines: 55 Okay, I've got GNUS up and running in the pawl.rpi.edu network here and there are just a couple of quick notes: a) it was up and running without many hassles at all. That's one thing I love about GNU. :-) b) well, actually, it wasn't no hassles ... tut.cis.ohio-state.edu probably saw me take it all of five or maybe six times; originally, the filename wasn't obviously a tar file, but Bob fixed that after I whined to him about my troubles. (Thanks, Bob) c) I tried C-d (gnus-Subject-rmail-digest) on Risks, hoping to watch some magic bursting, but it came back and said that the article was not a digest. It is obviously expecting a different format or somethin but I've not taken yet taken the time to look it up. Before I do, can anyone offer a few words of wisdom about how come PGN's Risks Digest isn't a digest? d) In order to prevent the least amount of headaches for people that I am ever-trying to convert to GNU Emacs, I will be writing a couple of elisp functions to automagically convert rn's KILL files to GNUS KILL files, to switch down the ~/News directory paths and bring everything back up in a non-hierarchal manner, and to save them the big surprise that I got the first time I ran GNUS. The surprise I got was that all of the groups which were not in my .newsrc came flooding in, inserted at the beginning, with lots of articles to read. Now, the reason that 80% of them weren't there was because I didn't want them cluttering my file. The other 20% I had never head of and would have appreciated a half a second mor to peruse and decide whether I wanted them. I found out about the options line supported by Bnews and GNUS, but the example it gave was sort of limited. I'll see what I can conjure up from it (like whether !comp.lang will allow all the comp.land groups to be missing) but I'd appreciate a summary of syntax if anyoen can provide it. I have to go diving into the code right now hoping that there is some hook provided around this autosubscription function, or that it is just a function in itself so I can easily rewrite it, that requires your approval before subscribing you, puts it in your option line if necessary, blah blah, etcetera. This is all part of a somewhat local one-man effort to educate users on the merits of the FSF and the shortcomings of vi. The way some people whine about things around here if all of a sudden something different and unexpected happens, I like to make it as user-friendly as possible (another Not Unix kind of thing ... :-). If anyone has any utilities that already do something like this, please let me know soon. If not, I'll post mine in less than a week. Thanks in advance. Dave -- tale@rpitsmts.bitnet, tale%mts@rpitsgw.rpi.edu, tale@pawl.rpi.edu