From xemacs-m  Tue Apr  8 05:57:11 1997
Received: from elc1.dina.kvl.dk (elc1.dina.kvl.dk [130.225.40.228])
	by xemacs.org (8.8.5/8.8.5) with SMTP id FAA25502
	for <xemacs-beta@xemacs.org>; Tue, 8 Apr 1997 05:57:09 -0500 (CDT)
Received: from zuse.dina.kvl.dk (zuse.dina.kvl.dk [130.225.40.245]) by elc1.dina.kvl.dk (8.6.12/8.6.4) with ESMTP id MAA19962; Tue, 8 Apr 1997 12:45:44 +0200
Received: (abraham@localhost) by zuse.dina.kvl.dk (8.6.12/8.6.4) id MAA20346; Tue, 8 Apr 1997 12:56:58 +0200
Sender: abraham@dina.kvl.dk
To: mac@silicon-sorcery.com
Cc: David Moore <dmoore@ucsd.edu>, xemacs-beta@xemacs.org
Subject: Re: xemacs "flavours" of packages
References: <rvvi5yxw4m.fsf@sdnp5.ucsd.edu> <199704080037.RAA27172@mage.silicon-sorcery.com>
Organization: The Church of Emacs
X-Face: +kRV2]2q}lixHkE{U)mY#+6]{AH=yN~S9@IFiOa@X6?GM<U{B+4e{k79.Ya{~':DblFPCg$
 @60,BfLv2@SKZ19cMWK0/C'v;tM:|6B'R}U1rp6CL&kN({9<zF/V{:JCg27yC)9oZjeqcQawzKfiNL
 t9}`vjmK["dRQC/qGFQq"%u|Q`:6{"Rz}b(dnl_"3$Jtqimi>|8MBp/
From: Per Abrahamsen <abraham@dina.kvl.dk>
Date: 08 Apr 1997 12:56:58 +0200
In-Reply-To: 's message of Mon, 7 Apr 1997 17:37:11 -0700 (PDT)
Message-ID: <rj4tdhu6it.fsf@zuse.dina.kvl.dk>
Lines: 32
X-Mailer: Gnus v5.4.37/Emacs 19.34
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

<mac@silicon-sorcery.com> writes:

> I've added custom support to the package I support (a mode for editing
> Verilog programs) and hung it at Custom->Emacs->Programming->Languages
> which you'll agree is the right place.
 
Yes.

[ ... ]

> There are 1015 elisp files; if every one of those gets a customize
> menu, we are going to get lost!!!

Why?  All 1015 elisp files will not be under 

	Custom->Emacs->Programming->Languages

hopefully only those that deal with programming languages.  And there
should only be one entry for each supported programming language.
That is probably still a lot (emacs is a programmers editor before
everything else), but I think it should be manageable.


> Possibility one: How about someone whip up some code that places in

> Possibility two: We set a coding style that states that modes that

I suggest that all packages which define their own menus, add a menu
entry for customizing themselves.  That should be easy with a call to
`custom-menu-create' in the menu definition. I'll think I'll add one
to customize itself, as an example of how to do it.

