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: .emacs-settings.el Date: Mon, 10 Sep 2007 09:08:17 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: References: <60282.128.165.123.18.1189002441.squirrel@webmail.lanl.gov> <87k5r350o5.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1189483377 14641 80.91.229.12 (11 Sep 2007 04:02:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 Sep 2007 04:02:57 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 11 14:02:44 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 1IV4Rg-00017w-26 for ged-emacs-devel@m.gmane.org; Tue, 11 Sep 2007 14:02:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUwxJ-0000IF-BA for ged-emacs-devel@m.gmane.org; Tue, 11 Sep 2007 00:02:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IUwvj-0007Aa-Ad for emacs-devel@gnu.org; Tue, 11 Sep 2007 00:00:51 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IUwvi-00078A-2g for emacs-devel@gnu.org; Tue, 11 Sep 2007 00:00:50 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IUwvh-00077u-Qj for emacs-devel@gnu.org; Tue, 11 Sep 2007 00:00:49 -0400 Original-Received: from main.gmane.org ([80.91.229.2] 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 1IUwvh-0002xp-7c for emacs-devel@gnu.org; Tue, 11 Sep 2007 00:00:49 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IUmIV-0007O3-Rd for emacs-devel@gnu.org; Mon, 10 Sep 2007 18:39:39 +0200 Original-Received: from c-24-14-57-89.hsd1.il.comcast.net ([24.14.57.89]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Sep 2007 18:39:39 +0200 Original-Received: from tzz by c-24-14-57-89.hsd1.il.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 10 Sep 2007 18:39:39 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: c-24-14-57-89.hsd1.il.comcast.net 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.110007 (No Gnus v0.7) Emacs/22.1.50 (darwin) Cancel-Lock: sha1:SHKzpTib56TOrEnqt6+7jgRMU9U= X-UiO-SPF-Received: Received-SPF: pass (mail-mx2.uio.no: domain of sea.gmane.org designates 80.91.229.5 as permitted sender) client-ip=80.91.229.5; envelope-from=news@sea.gmane.org; helo=sea.gmane.org; X-UiO-Spam-info: not spam, SpamAssassin (score=-3.0, required=12.0, autolearn=disabled, UIO_RECEIVED_FROM_NORWAY=-3) X-UiO-Scanned: D9E7750DAA2701DEE38D395F0C7E97D1412FBBC4 X-UiO-SPAM-Test: remote_host: 80.91.229.5 spam_score: -29 maxlevel 200 minaction 2 bait 0 mail/h: 9 total 389 max/h 30 blacklist 0 greylist 0 ratelimit 0 X-Detected-Kernel: 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:78555 Archived-At: On Sun, 09 Sep 2007 16:06:14 -0400 Stefan Monnier wrote: Stefan> I don't think it's a necessary feature, but it would be a nice Stefan> addition (for for file-local and dir-local settings). I'm not Stefan> sure how to implement it either, but I guess we could change Stefan> hack-local-variables to maintain a new (buffer-local) variable Stefan> `file-local-settings' and in C-h v we check this var to see if Stefan> the variable displayed is among the ones that were set Stefan> file-locally. >> I was thinking about this, and it occurred to me that we could have >> "false positives". E.g., project.el might set the variable and add it SM> Of course. The obvious solution is to record to value set, so if the value SM> is still the same, you can reasonably presume that there's still SM> a relationship between the setting and the variable's current value. SM> Of course, maybe there isn't, but most likely if the setting is a problem, SM> the user will see "this setting comes from ...", it will go there, remove SM> the file-local or project-local setting and try again and will then see that SM> the same problem is still present but without the "this setting comes from SM> ..." at which it'll know that there's something more to it. What about recording a stack of modifications, e.g. this variable was created in x.el line 300 it was modified by Customize in y.el line 400 it was overridden by a buffer-local version in z.el line 500 (file and line are not always available) I don't know how hard it is to implement this, but it would be great for general debugging too. If the new value of the variable could be recorded as well (optionally), this would be even more useful. Ted