From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: require-final-newline
Date: Sun, 06 Mar 2005 14:10:46 -0500 [thread overview]
Message-ID: <E1D819K-0003Jg-PD@fencepost.gnu.org> (raw)
In-Reply-To: <200503051953.j25JrS610363@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 5 Mar 2005 13:53:28 -0600 (CST))
In Emacs 21.3, Text mode did not override the default value of
require-final-newline. In current CVS, it does via
mode-require-final-newline. Is there a reason for that?
I don't remember the reason, but I remember there was one.
I think that specific point was discussed in this list
a few months ago.
Also, nil _is_ a valid value for mode-require-final-newline. But the
docstring is not very explicit about that and you can not set it to
nil via Custom. If you set it to nil outside Custom, Custom will
falsely describe the value as `ask', which is a bug.
I will fix that.
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.
next prev parent reply other threads:[~2005-03-06 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 19:53 require-final-newline Luc Teirlinck
2005-03-06 19:10 ` Richard Stallman [this message]
2005-03-07 1:29 ` require-final-newline Luc Teirlinck
2005-03-07 1:41 ` require-final-newline Stefan Monnier
2005-03-08 2:51 ` require-final-newline Richard Stallman
2005-03-07 1:41 ` require-final-newline Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2007-05-21 2:03 require-final-newline Trent Buck
2007-05-22 7:34 ` require-final-newline Carsten Dominik
2007-05-23 9:18 ` require-final-newline Trent Buck
2007-05-23 14:15 ` require-final-newline Carsten Dominik
2007-05-23 15:20 ` require-final-newline Trent Buck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1D819K-0003Jg-PD@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.