From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11654 Path: main.gmane.org!not-for-mail From: Jason R Mastaler Newsgroups: gmane.emacs.gnus.general Subject: Re: Quo Vadis, Quassia? Date: 15 Jul 1997 14:18:06 -0600 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035151329 31691 80.91.224.250 (20 Oct 2002 22:02:09 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:02:09 +0000 (UTC) Return-Path: Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by altair.xemacs.org (8.8.6/8.8.6) with ESMTP id OAA22154 for ; Tue, 15 Jul 1997 14:44:58 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id QAA16510 for ; Tue, 15 Jul 1997 16:28:19 -0500 (CDT) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Tue, 15 Jul 1997 22:18:58 +0200 Original-Received: (qmail 5696 invoked by uid 504); 15 Jul 1997 20:18:56 -0000 Original-Received: (qmail 5693 invoked from network); 15 Jul 1997 20:18:56 -0000 Original-Received: from brickbat8.mindspring.com (207.69.200.11) by claymore.vcinet.com with SMTP; 15 Jul 1997 20:18:56 -0000 Original-Received: from ashanti.mastaler.com (ip43.albuquerque.nm.pub-ip.psi.net [38.11.185.43]) by brickbat8.mindspring.com (8.8.5/8.8.5) with ESMTP id QAA00412 for ; Tue, 15 Jul 1997 16:18:51 -0400 (EDT) Original-Received: (from jason@localhost) by ashanti.mastaler.com (8.8.5/8.8.5) id OAA24696; Tue, 15 Jul 1997 14:18:07 -0600 (MDT) Original-To: ding@gnus.org In-Reply-To: Eze Ogwuma's message of "15 Jul 1997 15:18:34 +0100" X-Mailer: Gnus v5.4.63/XEmacs 19.15 Original-Lines: 63 Original-Xref: altair.xemacs.org dgnus-list:2044 Xref: main.gmane.org gmane.emacs.gnus.general:11654 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11654 Eze Ogwuma writes: > Where's the "Compatibility" section? I can't see it. Search for it in the info pages Index. ================== File: gnus, Node: Compatibility, Next: Conformity, Prev: Why?, Up: History Compatibility ------------- Gnus was designed to be fully compatible with GNUS. Almost all key bindings have been kept. More key bindings have been added, of course, but only in one or two obscure cases have old bindings been changed. Our motto is: In a cloud bones of steel. All commands have kept their names. Some internal functions have changed their names. The `gnus-uu' package has changed drastically. *See Decoding Articles::. One major compatibility question is the presence of several summary buffers. All variables relevant while reading a group are buffer-local to the summary buffer they belong in. Although many important variables have their values copied into their global counterparts whenever a command is executed in the summary buffer, this change might lead to incorrect values being used unless you are careful. All code that relies on knowledge of GNUS internals will probably fail. To take two examples: Sorting `gnus-newsrc-alist' (or changing it in any way, as a matter of fact) is strictly verboten. Gnus maintains a hash table that points to the entries in this alist (which speeds up many functions), and changing the alist directly will lead to peculiar results. Old hilit19 code does not work at all. In fact, you should probably remove all hilit code from all Gnus hooks (`gnus-group-prepare-hook' and `gnus-summary-prepare-hook'). Gnus provides various integrated functions for highlighting. These are faster and more accurate. To make life easier for everybody, Gnus will by default remove all hilit calls from all hilit hooks. Uncleanliness! Away! Packages like `expire-kill' will no longer work. As a matter of fact, you should probably remove all old GNUS packages (and other code) when you start using Gnus. More likely than not, Gnus already does what you have written code to make GNUS do. (Snicker.) Even though old methods of doing things are still supported, only the new methods are documented in this manual. If you detect a new method of doing something while reading this manual, that does not mean you have to stop doing it the old way. Gnus understands all GNUS startup files. Overall, a casual user who hasn't written much code that depends on GNUS internals should suffer no problems. If problems occur, please let me know by issuing that magic command `M-x gnus-bug'.