From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: files.el: Patch to make project-settings optional/customizable Date: Thu, 13 Nov 2008 13:26:40 -0500 Message-ID: <871vxflbxb.fsf@cyd.mit.edu> References: <5f0ff9220811130629t505badf9kb1bcc380df89a08f@mail.gmail.com> <87y6zn4pqw.fsf@cyd.mit.edu> <200811131607.mADG71u6010167@mothra.ics.uci.edu> <200811131619.mADGJukm010206@mothra.ics.uci.edu> <87prkz4kgh.fsf@cyd.mit.edu> <200811131728.mADHSH2M010654@mothra.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1226600815 31522 80.91.229.12 (13 Nov 2008 18:26:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Nov 2008 18:26:55 +0000 (UTC) Cc: Tom Tromey , "T.V. Raman" , emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 13 19:27:56 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 1L0guw-0002iH-Lg for ged-emacs-devel@m.gmane.org; Thu, 13 Nov 2008 19:27:46 +0100 Original-Received: from localhost ([127.0.0.1]:48630 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L0gto-0003vk-KJ for ged-emacs-devel@m.gmane.org; Thu, 13 Nov 2008 13:26:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L0gtj-0003vL-Ld for emacs-devel@gnu.org; Thu, 13 Nov 2008 13:26:31 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L0gtf-0003sq-RR for emacs-devel@gnu.org; Thu, 13 Nov 2008 13:26:30 -0500 Original-Received: from [199.232.76.173] (port=43376 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L0gtf-0003sn-Kc for emacs-devel@gnu.org; Thu, 13 Nov 2008 13:26:27 -0500 Original-Received: from cyd.mit.edu ([18.115.2.24]:33276) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L0gtf-0000Kf-Eq for emacs-devel@gnu.org; Thu, 13 Nov 2008 13:26:27 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id F2DBE57E09E; Thu, 13 Nov 2008 13:26:40 -0500 (EST) In-Reply-To: <200811131728.mADHSH2M010654@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Thu, 13 Nov 2008 09:28:17 -0800 (PST)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (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:105661 Archived-At: Dan Nicolaescu writes: > > I think it's generally good policy to avoid hardcoding file names. > > But general policy should not be applied without thinking about the > particulars of each case. As Tom said, there were some long > discussions about this, and I think that the opposite conclusion was > reached _for this particular case_. Just undoing that decision > without reviewing the previous discussions on this does not seem like > a good idea. I can't seem to find the discussion. Could you point me to it? (Even if we decide to hardcode the name, which I'm not convinced about, there needs to be a comment in the code explaining why.)