From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Blunderbuss ".dir-locals.el" raises everything in its path!! Date: Tue, 14 Jul 2009 14:21:29 -0400 Message-ID: References: <20090712144137.GB2524@muc.de> <87hbxhony6.fsf@stupidchicken.com> <20090712180623.GA1009@muc.de> <87k52dycha.fsf@stupidchicken.com> <4A5C2C96.4080802@swipnet.se> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1247595694 1742 80.91.229.12 (14 Jul 2009 18:21:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 14 Jul 2009 18:21:34 +0000 (UTC) Cc: Alan Mackenzie , Chong Yidong , emacs-devel@gnu.org To: Jan =?iso-8859-1?Q?Dj=E4rv?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 14 20:21:27 2009 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 1MQmd4-0000EE-Un for ged-emacs-devel@m.gmane.org; Tue, 14 Jul 2009 20:21:27 +0200 Original-Received: from localhost ([127.0.0.1]:58945 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MQmd4-00073H-2i for ged-emacs-devel@m.gmane.org; Tue, 14 Jul 2009 14:21:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MQmcz-00073C-MS for emacs-devel@gnu.org; Tue, 14 Jul 2009 14:21:21 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MQmcu-000730-Gd for emacs-devel@gnu.org; Tue, 14 Jul 2009 14:21:20 -0400 Original-Received: from [199.232.76.173] (port=48832 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MQmcu-00072x-CN for emacs-devel@gnu.org; Tue, 14 Jul 2009 14:21:16 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:7065) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MQmcu-0001DA-3K for emacs-devel@gnu.org; Tue, 14 Jul 2009 14:21:16 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Au4EAC9pXEpMCpbp/2dsb2JhbACBUdB/gj2BSwWGbg X-IronPort-AV: E=Sophos;i="4.42,398,1243828800"; d="scan'208";a="41577394" Original-Received: from 76-10-150-233.dsl.teksavvy.com (HELO pastel.home) ([76.10.150.233]) by ironport2-out.teksavvy.com with ESMTP; 14 Jul 2009 14:21:15 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id DF66C7EF7; Tue, 14 Jul 2009 14:21:29 -0400 (EDT) In-Reply-To: <4A5C2C96.4080802@swipnet.se> ("Jan =?iso-8859-1?Q?Dj=E4rv=22?= =?iso-8859-1?Q?'s?= message of "Tue, 14 Jul 2009 08:58:30 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:112457 Archived-At: >>>> In particular, the File Style and local variables settings are rarely >>>> used precision instruments, for configuring unusual files unusually. >>> This indicates that we should not set c-file-style in the .dir-locals.el >>> file of the Emacs source tree. >> Actually, I wonder: why would it be correct to use another style than GNU >> for C files inside the Emacs source tree? >> I don't think it's a feature that dir-locals.el takes precedence over >> mode-hooks (it's more of an accident that we consider sufficiently >> harmless not to fix it, especially since a fix would probably be >> difficult/inconvenient/buggy), but in this case it seems to provide just >> the behavior we want. I mean we do want to "impose" the GNU style in >> our files, no matter what the user usually prefers. >> What am I missing? > That setting space-before-funcall in c-cleanup-list is a very reasonable > thing to do in the context of the GNU-style (why isn't it on by default for > GNU?), and in no way breaks the imposed style. But the old ways of doing > that in the Emacs source tree doesn't work anymore, and there is nothing in > NEWS, and AFAIK, no discussion about it has taken place. It is just one of > those frustrating WTF-discoveries. Doesn't this rather point to a problem in C-mode's interaction between its various config variables? Stefan