From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "T. V. Raman" Newsgroups: gmane.emacs.devel Subject: Re: .emacs-settings.el Date: Sat, 8 Sep 2007 12:19:50 -0700 Message-ID: <18146.62934.388958.194074@gargle.gargle.HOWL> References: <60282.128.165.123.18.1189002441.squirrel@webmail.lanl.gov> <87k5r350o5.fsf@jurta.org> Reply-To: raman@users.sf.net NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1189279206 16211 80.91.229.12 (8 Sep 2007 19:20:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 8 Sep 2007 19:20:06 +0000 (UTC) Cc: tzz@lifelogs.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: tromey@redhat.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 08 21:20:05 2007 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 1IU5qY-00077h-Kn for ged-emacs-devel@m.gmane.org; Sat, 08 Sep 2007 21:19:58 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IU5qW-0007kd-6q for ged-emacs-devel@m.gmane.org; Sat, 08 Sep 2007 15:19:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IU5qS-0007k9-W0 for emacs-devel@gnu.org; Sat, 08 Sep 2007 15:19:53 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IU5qS-0007jx-Au for emacs-devel@gnu.org; Sat, 08 Sep 2007 15:19:52 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IU5qS-0007ju-5G for emacs-devel@gnu.org; Sat, 08 Sep 2007 15:19:52 -0400 Original-Received: from alnrmhc16.comcast.net ([204.127.225.96]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IU5qR-0000EW-Rp for emacs-devel@gnu.org; Sat, 08 Sep 2007 15:19:51 -0400 Original-Received: from localhost (c-71-202-191-236.hsd1.ca.comcast.net[71.202.191.236]) by comcast.net (alnrmhc16) with ESMTP id <20070908191950b1600bovuee>; Sat, 8 Sep 2007 19:19:51 +0000 Original-Received: by localhost (Postfix, from userid 1000) id 6A0FA12A4546; Sat, 8 Sep 2007 12:19:50 -0700 (PDT) In-Reply-To: X-Mailer: VM alpha-478 under Emacs 23.0.50.9 (i686-pc-linux-gnu) x-attribution: tvr X-Detected-Kernel: Solaris 10 (1203?) 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:78282 Archived-At: while we think of project specific settings, it would also be nice to see if we could create the ability to export a set of related options from custom. The new custom-themes support is nice, but it's still difficult to do the following: 0) once you have customized a complex package, say JDEE or org, it's difficult to export out settings for just that package into a theme that you might then take to another machine. 2) With the custom file getting large, it's increasingly creating a single point of failure, and I've also noticed that once in a while some settings get inexplicably lost. As we do project specific settings, it would be really nice to be first able to refactor a large custom file into a set of package-specific files, this will make tracking down sources of multiple settings much easier. >>>>> "Tom" == Tom Tromey writes: >>>>>> "Stefan" == Stefan Monnier >>>>>> writes: Tom> [ C-h v output ] Tom> Stefan> I don't think it's a necessary feature, but it would Stefan> be a nice addition (for for file-local and dir-local Stefan> settings). I'm not sure how to implement it either, Stefan> but I guess we could change hack-local-variables to Stefan> maintain a new (buffer-local) variable Stefan> `file-local-settings' and in C-h v we check this var Stefan> to see if the variable displayed is among the ones Stefan> that were set file-locally. Tom> Tom> I was thinking about this, and it occurred to me that we Tom> could have "false positives". E.g., project.el might Tom> set the variable and add it to file-local-settings, but Tom> then some later hook might setq the variable as well. Tom> In this situation C-h v would incorrectly say that the Tom> variable had a project setting -- unless every setq Tom> manipulated file-local-settings. The reason this is bad Tom> is that the point of mentioning this in C-h v is to Tom> avoid confusion resulting variables magically being set Tom> -- but in this situation you would be just as confused Tom> trying (mistakenly) to debug your .emacs-settings.el. Tom> Tom> Tom Tom> Tom> Tom> _______________________________________________ Tom> Emacs-devel mailing list Emacs-devel@gnu.org Tom> http://lists.gnu.org/mailman/listinfo/emacs-devel -- Best Regards, --raman Email: raman@users.sf.net WWW: http://emacspeak.sf.net/raman/ AIM: emacspeak GTalk: tv.raman.tv@gmail.com PGP: http://emacspeak.sf.net/raman/raman-almaden.asc Google: tv+raman IRC: irc://irc.freenode.net/#emacs