Path: utzoo!attcan!uunet!convex!killer!ames!mailrus!tut.cis.ohio-state.edu!triceratops.cis.ohio-state.edu!karl From: karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) Newsgroups: comp.emacs Subject: Obnoxious lisp code Message-ID: Date: 19 Nov 88 05:30:17 GMT References: <32408@bbn.COM> <1466@nmtsun.nmt.edu> Sender: news@tut.cis.ohio-state.edu Organization: OSU Lines: 29 In-reply-to: dieter@titan.nmt.edu's message of 17 Nov 88 21:47:28 GMT dieter@titan.nmt.edu (The Demented Teddy Bear) writes: > "He even writes obnoxious LISP CODE!" > -- A local Lisp hacker and AI expert, having tried > (thus far unsuccessfully) to bring up Gnews 2.0. And seems to ignore questions about it. What troubles are you having? An amazing thing was learned today about Gnews: It gets just all upset if rnews is loaded before Gnews. Matthew's reasoning on not avoiding conflicts between Gnews and rnews is that one can't possibly need both at the same time. Or something like that. And he's right. But we'd been pre-loading rnews and rnewspost at build time for a long, long time, so it was always already present when Gnews loaded up, which caused Gnews to notice that there already existed a news-mode-map, which meant that it didn't bother to initialize news-mode-map, which was wrong... The fix (thanx, Matthew) was to (setq news-mode-map nil) before loading Init. And we won't be pre-loading rnews during build any more. It'll still autoload, of course, for the truly backward folk still using it. Gnews is now officially installed here. BTW, Matthew seems to have found that .signature file pretty amusing for the short while that I had it. --Karl