From xemacs-m  Fri Mar 28 18:16:44 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA13199
	for <xemacs-beta@xemacs.org>; Fri, 28 Mar 1997 18:16:42 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQciwv29198; Fri, 28 Mar 1997 19:16:42 -0500 (EST)
Date: Fri, 28 Mar 1997 19:16:42 -0500 (EST)
Message-Id: <QQciwv29198.199703290016@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: migrating from .xemacs-options to customize
In-Reply-To: <rjd8sj517y.fsf@zuse.dina.kvl.dk>
References: <199703280336.UAA20369@branagh.ta52.lanl.gov>
	<rjiv2c5pnv.fsf@zuse.dina.kvl.dk>
	<199703281643.JAA21648@branagh.ta52.lanl.gov>
	<rjd8sj517y.fsf@zuse.dina.kvl.dk>
X-Mailer: VM 6.23 under 19.15 XEmacs Lucid
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Per Abrahamsen writes:
 > 
 > "John A. Turner" <turner@branagh.ta52.lanl.gov> writes:
 > 
 > > OK, went and tried.  Modified a face with edit-faces, did Save
 > > Options, and it wrote out a new .xemacs-options with no face-setting
 > > stuff at all.  Just wiped it all out.  Glad I saved it first.
 > 
 > Just download the xemacs-19.15-sparc-sun-solaris2.4 binary kit to test
 > it out.
 > 
 > Apparently you have to 
 > 
 > 	(setq options-save-faces t)
 > 
 > if you want to avoid having XEmacs silently throw away all your face
 > customizations when you save the options the first time.
 > 
 > ...
 > 
 > Now how does one best express grave concern about a technical
 > decision, without putting down the hard work and good intention of the
 > people who made it?
 > 
 > > It looks like it comes up using the faces that were set by
 > > .xemacs-options.  What I'd like to do then is Save this setup for
 > > customize to use later.
 > 
 > You can not do that.  Custom doesn't work that way.  
 > It wasn't really designed for editing random faces.

How hard could it be?  What we need is something that takes a face as
an argument and generates the spec list that custom-set-faces wants.
We then declare all the relevant faces with custom-declare-face, call
custome-set-faces with this list and then call whatever the custom
save function is.  Yes?

