all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: comment-multi-line docstring
Date: Sat, 25 Sep 2004 15:33:31 -0400	[thread overview]
Message-ID: <m17jqitapm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200409251828.i8PISNv18628@raven.dms.auburn.edu> (Luc Teirlinck's message of "Sat, 25 Sep 2004 13:28:23 -0500 (CDT)")

> From C-h v comment-multi-line:

>     *Non-nil means M-x comment-indent-new-line continues comments, with no
>      new terminator or starter.
>     This is obsolete because you might as well use C-j.

> Is that "This is obsolete" really accurate?

I think it isn't.

IIRC, when I wrote newcomment.el I was pretty concerned about backward
compatibility (I wanted to make sure that the package was going to be
accepted as a *replacement* for the old commenting code, rather than
like cperl-mode and ibuffer), so I preserved everything as much as I could.
This variable was one I didn't understand at the time, so I just did my best
to preserve the behavior (without actually knowing it, so it was basically
preserving the code) and touched it as little as possible.

I've since learned a bit more about this variable (mostly thanks to
bug reports from Martin Stjernholm) which seems to be actually used
by default in CC-mode and which I've since also used in sgml-mode.

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.


        Stefan

  parent reply	other threads:[~2004-09-25 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-25 18:28 comment-multi-line docstring Luc Teirlinck
2004-09-25 19:09 ` Luc Teirlinck
2004-09-25 19:33 ` Stefan [this message]
2004-09-26 22:47   ` Luc Teirlinck

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=m17jqitapm.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.