unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: rms@gnu.org
Cc: David O'Toole <dto@gnu.org>, emacs-devel@gnu.org
Subject: Re: comment-add
Date: Tue, 06 Nov 2007 21:59:34 +0100	[thread overview]
Message-ID: <87prynum2x.fsf@baldur.tsdh.de> (raw)
In-Reply-To: <E1IaJwS-0008UB-2z@fencepost.gnu.org> (Richard Stallman's message of "Tue, 25 Sep 2007 19:35:48 -0400")

Richard Stallman <rms@gnu.org> writes:

>     I noticed the new default behavior and didn't like it---it turns
>     every line of the commented region into a headline matching
>     outline-regexp (and gets font-locked due to some snippets in my
>     .emacs). Is this really what was intended?
>
> That is a peculiar advanced usage mode, not a significant factor for a
> decision about defaults.

But the docs explicitly mention this "peculiar advanced usage mode".

,----[ (info "(elisp)Comment Tips") ]
| `;;;'
|      Comments that start with three semicolons, `;;;', should start at
|      the left margin.  These are used, occasionally, for comments within
|      functions that should start at the margin.  We also use them
|      sometimes for comments that are between functions--whether to use
|      two or three semicolons depends on whether the comment should be
|      considered a "heading" by Outline minor mode.  By default,
|      comments starting with at least three semicolons (followed by a
|      single space and a non-whitespace character) are considered
|      headings, comments starting with two or less are not.
| 
|      Another use for triple-semicolon comments is for commenting out
|      lines within a function.  We use three semicolons for this
|      precisely so that they remain at the left margin.  By default,
|      Outline minor mode does not consider a comment to be a heading
|      (even if it starts with at least three semicolons) if the
|      semicolons are followed by at least two spaces.  Thus, if you add
|      an introductory comment to the commented out code, make sure to
|      indent it by at least two spaces after the three semicolons.
| 
|           (defun foo (a)
|           ;;;  This is no longer necessary.
|           ;;;  (force-mode-line-update)
|             (message "Finished with %s" a))
| 
|      When commenting out entire functions, use two semicolons.
`----

Maybe we could all be happy if we change the new behavior to insert
three semicolons followed by two spaces?

Bye,
Tassilo

  reply	other threads:[~2007-11-06 20:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 22:55 comment-add Stephen Berman
2007-09-25  9:39 ` comment-add David O'Toole
2007-09-25 23:35   ` comment-add Richard Stallman
2007-11-06 20:59     ` Tassilo Horn [this message]
2007-12-10 15:19       ` comment-add Richard Stallman
2007-12-10 19:41         ` comment-add Tassilo Horn
2007-12-11 19:00           ` comment-add Richard Stallman
2007-12-11 20:34             ` comment-add Tassilo Horn
2007-12-15 21:36               ` comment-add Richard Stallman
2007-09-25 16:07 ` comment-add Stefan Monnier
2007-09-25 21:48   ` comment-add Eli Zaretskii
2007-09-25 17:57 ` comment-add Richard Stallman
2007-09-25 22:27   ` comment-add Leo

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=87prynum2x.fsf@baldur.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=dto@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).