From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: cc-mode adds newlines Date: Sat, 20 Nov 2004 09:13:33 +0900 Message-ID: References: <7joiybt7.fsf@blue.sea.net> <20041119231343.GA19603@apps.cwi.nl> Reply-To: snogglethorpe@gmail.com, miles@gnu.org NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1100909676 7324 80.91.229.6 (20 Nov 2004 00:14:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 20 Nov 2004 00:14:36 +0000 (UTC) Cc: Alan Mackenzie , Jari Aalto , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 20 01:14:30 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 1CVIta-0003xI-00 for ; Sat, 20 Nov 2004 01:14:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVJ2U-0001nR-Qn for ged-emacs-devel@m.gmane.org; Fri, 19 Nov 2004 19:23:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CVJ1i-0001fM-SG for emacs-devel@gnu.org; Fri, 19 Nov 2004 19:22:55 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CVJ1e-0001dg-Vv for emacs-devel@gnu.org; Fri, 19 Nov 2004 19:22:51 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVJ1e-0001cx-KD for emacs-devel@gnu.org; Fri, 19 Nov 2004 19:22:50 -0500 Original-Received: from [64.233.184.193] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CVIsg-0001Jc-3J for emacs-devel@gnu.org; Fri, 19 Nov 2004 19:13:34 -0500 Original-Received: by wproxy.gmail.com with SMTP id 40so64885wri for ; Fri, 19 Nov 2004 16:13:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=M+79VHsPc0r8bPgY+FZGXN5m9Rf3UMsWFcdj1do01mDQuhs+odCeW0OassiZshwNCc4PiPEy67APROdTWTfkdRp+oGGy96au18wS4Ao8InjClUNEub7Ou2lLRStKiSbqFNYN0soesJ7qF+GBDH/X6oaLeeOhLw4hZOaRqzQ5Vyc= Original-Received: by 10.54.20.74 with SMTP id 74mr96443wrt; Fri, 19 Nov 2004 16:13:33 -0800 (PST) Original-Received: by 10.54.19.70 with HTTP; Fri, 19 Nov 2004 16:13:33 -0800 (PST) Original-To: Andries Brouwer In-Reply-To: <20041119231343.GA19603@apps.cwi.nl> 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:30110 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30110 > That is a serious bug. It must ask by default. You're being extremely silly. It's absolutely not a "serious bug", and arguably it's not a bug at all. I expect most people would rather like being able to independently specify this feature for different modes -- while it's annoying for _all_ files to have a newline added (especially when editing e.g., binary files!), I think it's perfectly reasonable for _C_ files to have a final newline added by default. At most, I think think it's a documentation bug: it would be nice if you could know what's going on by looking at the documentation for `require-final-newline'. This suggests that maybe this feature really should be provided more centrally -- for instance what if `require-final-newline' could be an alist, allowing one to specify values for different modes, as well as a default, in a manner similar ot the way `c-require-final-newline' works now. -Miles