unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Paul D. Smith" <psmith@gnu.org>
Subject: Re: cc-mode adds newlines
Date: 22 Nov 2004 00:55:38 -0500	[thread overview]
Message-ID: <vpdr1xempgv9.fsf@lemming.engeast.baynetworks.com> (raw)
In-Reply-To: mailman.416.1101052189.27204.bug-gnu-emacs@gnu.org

%% Richard Stallman <rms@gnu.org> writes:

  rs> In the GNU Project we don't impose restrictions just because
  rs> someone else decided to.

That's fine for GCC and other GNU tools, but Emacs is not always used
to edit files which are only used with other GNU programs.

The C standard requires a newline.  It's probably not the only one.
Regardless of standards, there are tools out there which do not behave
properly if a file does not end in a newline.  Sometimes they even
misbehave _silently_.  And finally, I have a very hard time imagining a
situation where it's important to _NOT_ have a final newline in a text
file, especially a C source file (if your file is not a C file then you
shouldn't be editing it in C mode!)  I'm quite confident that the large
majority of users _WANT_ a newline at the end of their text files; I
really doubt that this can be creating real problems for anyone other
than a very tiny minority.


If the consensus is that modes shouldn't be setting this variable due to
philosophical thoughts about Emacs modifying files behind the user's
back that's OK, but if you change this behavior please replace it with a
simple, one-step operation to reinstate the current operation for the
modes where it makes sense (e.g. at least those that currently have it
set to t).  I don't think all those people should have to go create a
new mode hook for every mode that used to have this value set but no
longer does.  Maybe a new value for require-final-newline of 'text or
something where Emacs would just add the newline for text files (modes
might have to define this property somehow) without asking, and ask for
other files.


Anyway, that's my $0.02.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@gnu.org>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

  parent reply	other threads:[~2004-11-22  5:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3671.1100818498.8225.bug-gnu-emacs@gnu.org>
2004-11-18 23:23 ` cc-mode adds newlines Kevin Rodgers
2004-11-19  0:46   ` Andreas Schwab
2004-11-18 23:31 ` Jari Aalto
     [not found] ` <mailman.3684.1100821293.8225.bug-gnu-emacs@gnu.org>
2004-11-19  0:14   ` Stefan Monnier
2004-11-19 20:04     ` Richard Stallman
     [not found]     ` <mailman.56.1100895632.27204.bug-gnu-emacs@gnu.org>
2004-11-19 22:00       ` Hallvard B Furuseth
2004-11-21 15:38         ` Richard Stallman
     [not found]         ` <mailman.416.1101052189.27204.bug-gnu-emacs@gnu.org>
2004-11-22  5:55           ` Paul D. Smith [this message]
     [not found]           ` <mailman.619.1101127694.27204.bug-gnu-emacs@gnu.org>
2004-11-22 18:55             ` Stefan Monnier
     [not found]             ` <mailman.723.1101150150.27204.bug-gnu-emacs@gnu.org>
2004-11-22 19:37               ` Hallvard B Furuseth
2004-11-22 22:49                 ` Andreas Schwab
     [not found]                 ` <mailman.778.1101164414.27204.bug-gnu-emacs@gnu.org>
2004-11-28 19:39                   ` Hallvard B Furuseth
2004-11-18 22:45 Andries.Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2003-01-24  5:18 Luc Teirlinck
2003-01-24  2:41 Luc Teirlinck
2003-01-24  1:36 Luc Teirlinck
2003-01-25 19:22 ` Richard Stallman
     [not found] ` <mailman.985.1043522856.21513.bug-gnu-emacs@gnu.org>
2003-01-26 20:24   ` Benjamin Riefenstahl
     [not found] <mailman.884.1043357104.21513.bug-gnu-emacs@gnu.org>
2003-01-23 23:35 ` Benjamin Riefenstahl
2003-01-23 22:41 Luc Teirlinck
2003-01-23 21:52 Luc Teirlinck
2003-01-23 21:25 Luc Teirlinck
2003-01-23 13:17 Rommerskirchen Heinrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpdr1xempgv9.fsf@lemming.engeast.baynetworks.com \
    --to=psmith@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).