unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: <Andries.Brouwer@cwi.nl>
Subject: cc-mode adds newlines
Date: Thu, 18 Nov 2004 23:45:32 +0100 (MET)	[thread overview]
Message-ID: <200411182245.iAIMjWZ15062@apps.cwi.nl> (raw)

Working with emacs 21.3.
Struggled for a while to get emacs to save a file without final newline.

It is very bad that an editor decides to change my files behind
my back. If it asks "shall I add?", that is OK. If there is a
user variable that one can set so that it will never ask, that
is OK as well. But the default must always be not to damage
the user's files by doing "helpful" things.

OK. There is a variable require-final-newline.
But setting it did not make any difference.
The setting was overridden by cc-mode.el.

So, it looks like this aspect of emacs 21.3 is broken.

Asking Google I find a lot of discussion about the topic.
Apparently I am not the only one who hates it if the editor
changes files without having been asked to.
There is talk about c-require-final-newline as a variable,
or perhaps as an alist.

I see discussion about what languages have formal standards
that require source code lines to end with newline.
But that is all completely beside the point.
The point is: emacs must not start changing my files without
being asked. It doesnt do other things to my source code
(fortunately) to make it more "correct".
An editor must not "fix" my grammar, or spelling, or layout,
or anything at all in the source file without having been asked.

Andries

             reply	other threads:[~2004-11-18 22:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 22:45 Andries.Brouwer [this message]
     [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
     [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
  -- 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=200411182245.iAIMjWZ15062@apps.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    /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).