unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: mode-require-final-newline
Date: Wed, 30 Mar 2005 19:31:34 -0600 (CST)	[thread overview]
Message-ID: <200503310131.j2V1VYq06880@raven.dms.auburn.edu> (raw)

I believe that the docstring of `mode-require-newline' should also
explicitly mention the possibility of setting it to nil.  So now I
propose the following patch.  Compared to the previous patch, it only
adds one line to the docstring.

===File ~/files.el-diff-3===================================
*** files.el	28 Mar 2005 15:33:36 -0600	1.753
--- files.el	30 Mar 2005 19:14:26 -0600	
***************
*** 291,297 ****
    :group 'editing-basics)
  
  (defcustom mode-require-final-newline t
!   "*Whether to add a newline at the end of the file, in certain major modes.
  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.
--- 291,297 ----
    :group 'editing-basics)
  
  (defcustom mode-require-final-newline t
!   "*Whether to add a newline at end of file, in certain major modes.
  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.
***************
*** 299,308 ****
  A value of t means do this only when the file is about to be saved.
  A value of `visit' means do this right after the file is visited.
  A value of `visit-save' means do it at both of those times.
! Any other non-nil value means ask user whether to add a newline, when saving."
    :type '(choice (const :tag "When visiting" visit)
  		 (const :tag "When saving" t)
  		 (const :tag "When visiting or saving" visit-save)
  		 (other :tag "Ask" ask))
    :group 'editing-basics
    :version "22.1")
--- 299,310 ----
  A value of t means do this only when the file is about to be saved.
  A value of `visit' means do this right after the file is visited.
  A value of `visit-save' means do it at both of those times.
! Any other non-nil value means ask user whether to add a newline, when saving.
! nil means don't add newlines."
    :type '(choice (const :tag "When visiting" visit)
  		 (const :tag "When saving" t)
  		 (const :tag "When visiting or saving" visit-save)
+ 		 (const :tag "Never" nil)
  		 (other :tag "Ask" ask))
    :group 'editing-basics
    :version "22.1")
============================================================

             reply	other threads:[~2005-03-31  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  1:31 Luc Teirlinck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31  1:21 mode-require-final-newline Luc Teirlinck
2005-03-31  2:38 ` mode-require-final-newline Chong Yidong
2005-04-01  4:10   ` mode-require-final-newline Richard Stallman

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=200503310131.j2V1VYq06880@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    /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).