From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Andries Brouwer Newsgroups: gmane.emacs.devel Subject: Re: cc-mode adds newlines Date: Sun, 21 Nov 2004 14:28:04 +0100 Message-ID: <20041121132804.GJ20436@apps.cwi.nl> References: <20041121020850.GA20436@apps.cwi.nl> <20041121122629.GE20436@apps.cwi.nl> <20041121124911.GG20436@apps.cwi.nl> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1101043735 900 80.91.229.6 (21 Nov 2004 13:28:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 21 Nov 2004 13:28:55 +0000 (UTC) Cc: bug-cc-mode@gnu.org, Alan Mackenzie , Andries Brouwer , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 21 14:28:40 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CVrlg-0006gG-00 for ; Sun, 21 Nov 2004 14:28:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVrug-0002hO-Fq for ged-emacs-devel@m.gmane.org; Sun, 21 Nov 2004 08:37:58 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CVruX-0002gk-8h for emacs-devel@gnu.org; Sun, 21 Nov 2004 08:37:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CVruW-0002gM-E3 for emacs-devel@gnu.org; Sun, 21 Nov 2004 08:37:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVruW-0002g1-8a for emacs-devel@gnu.org; Sun, 21 Nov 2004 08:37:48 -0500 Original-Received: from [192.16.191.8] (helo=hera.cwi.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CVrl7-0005XT-VG; Sun, 21 Nov 2004 08:28:06 -0500 Original-Received: from apps.cwi.nl (apps.cwi.nl [192.16.191.34]) by hera.cwi.nl with ESMTP id iALDS4xh003580 for ; Sun, 21 Nov 2004 14:28:05 +0100 (MET) Original-Received: (from aeb@localhost) by apps.cwi.nl (8.11.7p1+Sun/8.12.2) id iALDS4M15128; Sun, 21 Nov 2004 14:28:04 +0100 (MET) Original-To: David Kastrup Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i 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: main.gmane.org gmane.emacs.devel:30165 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30165 On Sun, Nov 21, 2004 at 02:08:41PM +0100, David Kastrup wrote: > I don't particularly like the idea that every mode that has particular > requirements for a variable like that has to have a separately named > variable of its own: this makes it more difficult to figure out what > happens. I think that in the long run something more transparent for > mode-specific defaults should be found. Yes, indeed. There is a general discussion here on the use of mode variables, but I am afraid of commenting on that right now - like to avoid blowing up this small discussion into too many threads. Maybe later. My point today is: emacs must never unexpectedly change a file behind the user's back. That is, the default settings must be so that emacs asks before changing. This general principle applied to the final newline leads to a require-final-newline with default ask. I do not believe that it is meaningful to have a separate c-require-final-newline, but should it turn out that people exist that really want different behaviours depending on major mode, then for all major modes the default must again be ask (or the value of the global variable). Andries