From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: comment-add Date: Tue, 06 Nov 2007 21:59:34 +0100 Message-ID: <87prynum2x.fsf@baldur.tsdh.de> References: <87ir5zwu4j.fsf@escher.local.home> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1194382805 29248 80.91.229.12 (6 Nov 2007 21:00:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Nov 2007 21:00:05 +0000 (UTC) Cc: David O'Toole , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 06 22:00:07 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IpVWn-0008E3-D7 for ged-emacs-devel@m.gmane.org; Tue, 06 Nov 2007 22:00:05 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpVWc-0006iu-48 for ged-emacs-devel@m.gmane.org; Tue, 06 Nov 2007 15:59:54 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IpVWY-0006fR-Bn for emacs-devel@gnu.org; Tue, 06 Nov 2007 15:59:50 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpVWT-0006Ud-NR for emacs-devel@gnu.org; Tue, 06 Nov 2007 15:59:50 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpVWT-0006UT-Jj for emacs-devel@gnu.org; Tue, 06 Nov 2007 15:59:45 -0500 Original-Received: from out1.smtp.messagingengine.com ([66.111.4.25]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpVWM-0008SJ-7p; Tue, 06 Nov 2007 15:59:38 -0500 Original-Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id C88CD45C8E; Tue, 6 Nov 2007 15:59:37 -0500 (EST) Original-Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 06 Nov 2007 15:59:37 -0500 X-Sasl-enc: 8Z7h48Zixhs3wNXlC59w2d2dXVac9lbPCbJUySyr0f6B 1194382777 Original-Received: from baldur.tsdh.de (dslb-084-063-060-089.pools.arcor-ip.net [84.63.60.89]) by mail.messagingengine.com (Postfix) with ESMTP id 6C36AB987; Tue, 6 Nov 2007 15:59:36 -0500 (EST) Mail-Followup-To: rms@gnu.org, David O'Toole , emacs-devel@gnu.org In-Reply-To: (Richard Stallman's message of "Tue, 25 Sep 2007 19:35:48 -0400") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:82676 Archived-At: Richard Stallman 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