[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comment-multi-line docstring
From: |
Luc Teirlinck |
Subject: |
Re: comment-multi-line docstring |
Date: |
Sun, 26 Sep 2004 17:47:31 -0500 (CDT) |
Stefan Monnier wrote:
So I think the docstring should be rewritten to remove the `obsolete' part
and to better explain what it does. AFAIk, what it does it change
auto-fill-mode so that it doesn't add a "end+start" pair of comment markers
when breaking a line.
What about the following new docstring? Too bad that \\[...] does not
recognize aliases. I had to use \\[indent-new-comment-line] to get
C-M-j. \\[comment-indent-new-line] produced `M-x comment-indent-new-line'.
===File ~/newcomment-diff===================================
*** newcomment.el 07 Sep 2004 09:18:13 -0500 1.79
--- newcomment.el 26 Sep 2004 17:26:27 -0500
***************
*** 215,222 ****
;;;###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]."
:type 'boolean)
(defcustom comment-empty-lines nil
--- 215,227 ----
;;;###autoload
(defcustom comment-multi-line nil
! "*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
============================================================