From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: require-final-newline Date: Sun, 6 Mar 2005 19:41:51 -0600 (CST) Message-ID: <200503070141.j271fpj19436@raven.dms.auburn.edu> References: <200503051953.j25JrS610363@raven.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1110159455 7105 80.91.229.2 (7 Mar 2005 01:37:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 7 Mar 2005 01:37:35 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 07 02:37:34 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D87BZ-0000vi-Oh for ged-emacs-devel@m.gmane.org; Mon, 07 Mar 2005 02:37:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D87VF-0006LG-DP for ged-emacs-devel@m.gmane.org; Sun, 06 Mar 2005 20:57:49 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D87Ul-00067h-7q for emacs-devel@gnu.org; Sun, 06 Mar 2005 20:57:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D87Ui-00066B-KF for emacs-devel@gnu.org; Sun, 06 Mar 2005 20:57:17 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D87Uh-00065Y-KT for emacs-devel@gnu.org; Sun, 06 Mar 2005 20:57:15 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D87Fn-0004qY-Ry; Sun, 06 Mar 2005 20:41:52 -0500 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id j271fp9N014360; Sun, 6 Mar 2005 19:41:51 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j271fpj19436; Sun, 6 Mar 2005 19:41:51 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Sun, 06 Mar 2005 14:10:46 -0500) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34262 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34262 Richard Stallman wrote: Would it be good to have the docstring mention this explicitly and allow it to be set to nil via Custom with proper warning of the involved dangers I don't know how to make Custom issue warnings. I meant putting a warning message in the Custom buffer if nil is chosen from the value menu, using the :doc keyword. But on second thought, I do not believe that such a warning is necessary. The docstring of `mode-require-final-newline' already says: Those modes set `require-final-newline' to this value when you enable them. They do so because they are used for files that are supposed to end in newlines, and the question is how to arrange that. If the user sets the option to nil, he knows that he chooses to arrange for that by remembering to do it manually (or by using software that can handle files without final newline). Sincerely, Luc.