From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: bug#3370: 23.0.94; `comment-region' indents comment chars inappropriately Date: Mon, 25 May 2009 14:56:37 -0700 Message-ID: <5E5C09B3DBFB4C6B98C6903351B48B7E@us.oracle.com> References: <87prdynkm5.fsf@cyd.mit.edu><87tz3admt1.fsf@cyd.mit.edu> <4A19F427.40606@gnu.org><874ov9aivv.fsf@cyd.mit.edu><460B8A8EC0204F4A830B9EC10995A169@us.oracle.com><2425239E1D3C418886AD82BF7680D4BF@us.oracle.com> Reply-To: Drew Adams , 3370@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1243289391 15816 80.91.229.12 (25 May 2009 22:09:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 May 2009 22:09:51 +0000 (UTC) Cc: 'Dan Nicolaescu' , 'Chong Yidong' , rms@gnu.org, 3370@emacsbugs.donarmstrong.com To: "'Stefan Monnier'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue May 26 00:09:44 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1M8iMZ-00042g-SI for geb-bug-gnu-emacs@m.gmane.org; Tue, 26 May 2009 00:09:44 +0200 Original-Received: from localhost ([127.0.0.1]:33156 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8iMZ-0004sD-9k for geb-bug-gnu-emacs@m.gmane.org; Mon, 25 May 2009 18:09:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M8iMI-0004gL-B7 for bug-gnu-emacs@gnu.org; Mon, 25 May 2009 18:09:26 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M8iMD-0004eq-D9 for bug-gnu-emacs@gnu.org; Mon, 25 May 2009 18:09:25 -0400 Original-Received: from [199.232.76.173] (port=47234 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8iMD-0004ec-4a for bug-gnu-emacs@gnu.org; Mon, 25 May 2009 18:09:21 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:33690) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M8iMC-0003aB-0W for bug-gnu-emacs@gnu.org; Mon, 25 May 2009 18:09:20 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n4PM9BFQ019689; Mon, 25 May 2009 15:09:17 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.14.3/8.14.3/Submit) id n4PM05rh017303; Mon, 25 May 2009 15:00:05 -0700 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: "Drew Adams" Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Mon, 25 May 2009 22:00:05 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 3370 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 3370-submit@emacsbugs.donarmstrong.com id=B3370.124328859217125 (code B ref 3370); Mon, 25 May 2009 22:00:05 +0000 Original-Received: (at 3370) by emacsbugs.donarmstrong.com; 25 May 2009 21:56:32 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from acsinet12.oracle.com (acsinet12.oracle.com [141.146.126.234]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n4PLuSIJ017114 for <3370@emacsbugs.donarmstrong.com>; Mon, 25 May 2009 14:56:29 -0700 Original-Received: from rgminet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by acsinet12.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4PLu499014804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 May 2009 21:56:06 GMT Original-Received: from abhmt004.oracle.com (abhmt004.oracle.com [141.146.116.13]) by rgminet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4PLuLb3020319; Mon, 25 May 2009 21:56:22 GMT Original-Received: from dradamslap1 (/98.210.250.59) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 25 May 2009 14:56:17 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: Acndfue4brVChyFkTrOY6S52bZ7MlgAA1g8w X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: abhmt004.oracle.com [141.146.116.13] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090201.4A1B1402.036C:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Resent-Date: Mon, 25 May 2009 18:09:25 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:28157 Archived-At: > Yes, I know that. > > > Commenting out this line: > > `abcdef' > > gives this, prior to Emacs 23: > > ;; `abcdef' > > Commenting out the line is different from inserting a comment at the > > same level: > > ;; > > `abcdef' > > I know. Yet, most cases of commented-out code would use > > ;; `abcdef' No, that was not an example of commenting-out code. It was an example of inserting a comment - as I said. > Obviously, you don't like it, just like Richard doesn't like it. I do > believe you're in the minority, tho. No, you're mistaken. I don't really care one way or the other about it. The information that was missing (and is still missing) is about `comment-style' and `comment-styles'. You gave me a solution for the code I have, but still no explanation of `comment-style'. There is still no doc for it. I don't need to use a different value of `comment-style' for my own use interactively - I don't really care whether the commented lines are indented or not. (At least I don't have a preference at the moment.) My question was about use of `comment-region' in code, not interactively. See the original bug report's use case. The real bug I guess is that there is no explanation of `comment-style'. Whenever things like this change, there is the potential (almost the certainty) that existing code will break, as it did in my case. My real need, I came to realize here, is not that `comment-region' act, by default, as it did before, but that I know how to fix the broken code due to its behavior change. The answer was to bind `comment-style', as you suggested. But there is no explanation, hence no understanding, of that answer - no doc for `comment-style'. And, as I said, the doc string for `comment-style' (which is pretty much useless) refers to `comment-styles', which is not recognized (and therefore has no link).