From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/12265 Path: main.gmane.org!not-for-mail From: Mark Hovey Newsgroups: gmane.emacs.gnus.general Subject: Unbundling of custom Date: 22 Sep 1997 09:03:12 +0000 Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035151832 2837 80.91.224.250 (20 Oct 2002 22:10:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:10:32 +0000 (UTC) Return-Path: Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by altair.xemacs.org (8.8.7/8.8.7) with ESMTP id HAA00304 for ; Mon, 22 Sep 1997 07:13:44 -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 JAA02791 for ; Mon, 22 Sep 1997 09:09:37 -0500 (CDT) Original-Received: from cchan1.math.wesleyan.edu (cchan1.math.wesleyan.edu [129.133.30.47]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Mon, 22 Sep 1997 15:00:36 +0200 Original-Received: (from hovey@localhost) by cchan1.math.wesleyan.edu (8.8.5/8.8.5) id JAA00707; Mon, 22 Sep 1997 09:03:13 GMT Original-To: ding@ifi.uio.no Original-Lines: 16 X-Mailer: Quassia Gnus v0.8/Emacs 19.34 Xref: main.gmane.org gmane.emacs.gnus.general:12265 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:12265 My own experience with Quassia Gnus 0.9: I have custom, unbundled from gnus in its own subdirectory of ~/emacs. My .emacs sets load-path so that emacs sees this before its own 19.34 version of custom. But of course the makefile in gnus/lisp says to byte-compile using emacs -q, which means emacs does not know about my version of custom. So I recommend writing something to scan for the latest version of custom (by looking at the .emacs file and scanning directories in load-path), then use that in byte-compiling. This is basically what w3 does when you run its configure program. Of course, I can also edit the Makefile by hand, and maybe this is what you have to tell people to do. I understand the philosophical rationale for unbundling custom. But in terms of practical convenience, I think it is a mistake. Mark Hovey