From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: require-final-newline
Date: Sun, 6 Mar 2005 19:41:51 -0600 (CST) [thread overview]
Message-ID: <200503070141.j271fpj19436@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1D819K-0003Jg-PD@fencepost.gnu.org> (message from Richard Stallman on Sun, 06 Mar 2005 14:10:46 -0500)
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.
next prev parent reply other threads:[~2005-03-07 1:41 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 ` require-final-newline Richard Stallman
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 ` Luc Teirlinck [this message]
-- 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=200503070141.j271fpj19436@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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.