From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: :file keyword for Customize Date: Fri, 09 May 2008 09:01:17 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <86mymzpoeq.fsf@lifelogs.com> References: <004101c8b129$788cd490$0ab32382@us.oracle.com> <48232D95.3020304@gnu.org> <004501c8b12c$d10ce620$0ab32382@us.oracle.com> <48233394.5060205@gnu.org> <86d4nwr8vs.fsf@lifelogs.com> <000101c8b135$6d360920$0ab32382@us.oracle.com> <868wykr4o3.fsf@lifelogs.com> <001501c8b152$46d778a0$0ab32382@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1210341551 9504 80.91.229.12 (9 May 2008 13:59:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 9 May 2008 13:59:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 09 15:59:48 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JuT8Q-0001FZ-46 for ged-emacs-devel@m.gmane.org; Fri, 09 May 2008 15:59:42 +0200 Original-Received: from localhost ([127.0.0.1]:41235 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuT7h-0001fM-AO for ged-emacs-devel@m.gmane.org; Fri, 09 May 2008 09:58:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JuT6y-0001Tz-DI for emacs-devel@gnu.org; Fri, 09 May 2008 09:58:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JuT6v-0001Te-Ty for emacs-devel@gnu.org; Fri, 09 May 2008 09:58:11 -0400 Original-Received: from [199.232.76.173] (port=43566 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuT6v-0001TR-Hs for emacs-devel@gnu.org; Fri, 09 May 2008 09:58:09 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:49693 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JuT6v-0002u8-7B for emacs-devel@gnu.org; Fri, 09 May 2008 09:58:09 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JuT6t-0004ef-1N for emacs-devel@gnu.org; Fri, 09 May 2008 13:58:07 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 May 2008 13:58:07 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 May 2008 13:58:07 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 28 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:lQQwECLN9sY6idhJ2Jd/wcB1jHg= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:96884 Archived-At: On Thu, 8 May 2008 14:27:10 -0700 "Drew Adams" wrote: DA> What I was thinking was that library writers would typically provide DA> one or more user options or functions as the :file sexps - it is DA> those sexps that would then let users, in effect, determine the DA> :file values used. IOW, end users would not directly determine the DA> sexps used for :file, but they would ultimately determine the values DA> of those sexps in some way (defined by the programmer). ... DA> In what I imagine, programmers can do that as they like, using DA> whatever code they think is appropriate as the various :file DA> sexps. [...] They can do just about anything they think is DA> appropriate for their users. That seems really complicated, and still requires every package to do it explicitly. It seems like you're trying to set up a :filegroup option, really, which tells the Customize interface that some options should be logically grouped together when they are saved. I think defgroup does this logical grouping already for the vast majority of options, so it's a matter of saying "save this defgroup's variables in file X." That may be possible as an optional add-on package that doesn't change the way Customize works normally. The approach you proposed would, I think, require changes to the core Customize behavior instead so it's less desirable. Ted