diff lisp/newcomment.el @ 89991:6c1af301b455

Revision: miles@gnu.org--gnu-2004/emacs--unicode--0--patch-48 Merge from emacs--cvs-trunk--0 Patches applied: * miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-581 Fix exec-shield autoconf test * miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-582 - miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-584 Update from CVS * miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-585 Merge from gnus--rel--5.10 * miles@gnu.org--gnu-2004/emacs--cvs-trunk--0--patch-586 Update from CVS * miles@gnu.org--gnu-2004/gnus--rel--5.10--patch-38 Update from CVS
author Miles Bader <miles@gnu.org>
date Thu, 30 Sep 2004 01:20:39 +0000
parents cce1c0ee76ee 902c984fa20a
children 58db929d96c6
line wrap: on
line diff
--- a/lisp/newcomment.el	Wed Sep 29 09:54:59 2004 +0000
+++ b/lisp/newcomment.el	Thu Sep 30 01:20:39 2004 +0000
@@ -215,8 +215,13 @@
 
 ;;;###autoload
 (defcustom comment-multi-line nil
-  "*Non-nil means \\[comment-indent-new-line] continues comments, with no new terminator or starter.
-This is obsolete because you might as well use \\[newline-and-indent]."
+  "*Non-nil means `comment-indent-new-line' continues comments.
+That is, it inserts no new terminator or starter.
+This affects `auto-fill-mode', which is the main reason to
+customize this variable.
+
+It also affects \\[indent-new-comment-line].  However, if you want this
+behavior for explicit filling, you might as well use \\[newline-and-indent]."
   :type 'boolean)
 
 (defcustom comment-empty-lines nil