From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Bob" Newsgroups: gmane.emacs.bugs Subject: bug#5570: Emacs 23.1.91.1 C++ mode "ESC C-q" and TAB indenting issue. Date: Thu, 18 Feb 2010 07:53:34 -0800 Message-ID: <002101cab0b2$879ed0c0$96dc7240$@net> References: <000301caac36$0fc0b760$2f422620$@net> <87pr494md5.fsf@stupidchicken.com> <000e01caad1e$dcbfc560$963f5020$@net> <876360s8rw.fsf@stupidchicken.com> <20100214201006.GA6169@muc.de> <000001caae62$638af6c0$2aa0e440$@net> <20100216163923.GB3456@muc.de> <000301caaf36$d5f86100$81e92300$@net> <20100217094652.GC2392@muc.de> <000301caafef$f64d3520$e2e79f60$@net> <20100218151250.GD2671@muc.de> 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 1266510191 2664 80.91.229.12 (18 Feb 2010 16:23:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Feb 2010 16:23:11 +0000 (UTC) Cc: 'Chong Yidong' , 5570@debbugs.gnu.org To: "'Alan Mackenzie'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Feb 18 17:23:03 2010 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.69) (envelope-from ) id 1Ni99a-0008WN-IR for geb-bug-gnu-emacs@m.gmane.org; Thu, 18 Feb 2010 17:23:02 +0100 Original-Received: from localhost ([127.0.0.1]:47328 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ni99Z-0000Ig-TA for geb-bug-gnu-emacs@m.gmane.org; Thu, 18 Feb 2010 11:23:01 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ni99U-0000Ib-93 for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2010 11:22:56 -0500 Original-Received: from [140.186.70.92] (port=52082 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ni99T-0000I8-ES for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2010 11:22:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ni99P-000887-HT for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2010 11:22:53 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:57611) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ni99P-000883-Fm for bug-gnu-emacs@gnu.org; Thu, 18 Feb 2010 11:22:51 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1Ni8hW-0003fS-Dj; Thu, 18 Feb 2010 10:54:02 -0500 X-Loop: bug-gnu-emacs@gnu.org Resent-From: "Bob" Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 18 Feb 2010 15:54:02 +0000 Resent-Message-ID: Resent-Sender: bug-gnu-emacs@gnu.org X-Emacs-PR-Message: followup 5570 X-Emacs-PR-Package: emacs,cc-mode X-Emacs-PR-Keywords: Original-Received: via spool by 5570-submit@debbugs.gnu.org id=B5570.126650839514066 (code B ref 5570); Thu, 18 Feb 2010 15:54:02 +0000 Original-Received: (at 5570) by debbugs.gnu.org; 18 Feb 2010 15:53:15 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ni8gk-0003ep-Uk for submit@debbugs.gnu.org; Thu, 18 Feb 2010 10:53:15 -0500 Original-Received: from qmta02.emeryville.ca.mail.comcast.net ([76.96.30.24]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ni8gj-0003ei-BM for 5570@debbugs.gnu.org; Thu, 18 Feb 2010 10:53:13 -0500 Original-Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta02.emeryville.ca.mail.comcast.net with comcast id jTJd1d0061bwxycA2Tt9ub; Thu, 18 Feb 2010 15:53:09 +0000 Original-Received: from Cache ([71.202.16.94]) by omta18.emeryville.ca.mail.comcast.net with comcast id jTvC1d00R21mHQP8eTvDhb; Thu, 18 Feb 2010 15:55:13 +0000 In-Reply-To: <20100218151250.GD2671@muc.de> X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acqwq9MJ6N6j4wQIQ++jCnhX03lOVQABjc5w Content-Language: en-us X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Thu, 18 Feb 2010 10:54:02 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org 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:35174 Archived-At: Alan, That's good news! Please let me know when you get it fixed and I'd like to try it out. BTW, the indenting and paren matching is a world better than 21.2, esp. with regard to template '<' and '>' characters. Good job! Bob -----Original Message----- From: Alan Mackenzie [mailto:acm@muc.de] Sent: Thursday, February 18, 2010 7:13 AM To: Bob Cc: 'Chong Yidong'; 5570@debbugs.gnu.org Subject: Re: bug#5570: Emacs 23.1.91.1 C++ mode "ESC C-q" and TAB indenting issue. Hi, Bob, On Wed, Feb 17, 2010 at 08:40:36AM -0800, Bob wrote: > Alan, > Attached is "Foo.cpp" and "dribble" (if I did it correctly, dribble recorded > what I typed). > It illustrates a case where indentation is one level deeper than it should > be. (The other case we've been working on is one level shallower than it > should be). Maybe they are related? I suspect not, but who knows? :-( However, I can reproduce this bug; the dribble file and your CC Mode configuration file were utterly essential to my doing so. Thanks! > visit-file "Foo.cpp", note indentation for "class Bar" is too deep. Now, TAB > on the "class Bar" line the indentation corrects. If you reconstruct the > file from "dribble" you should see TAB on the "class Bar" line incorrectly > indents too deep. Yes. > My ".emacs" file sets indentation to 2 spaces. I would guess there is an > issue where > the default (I think 4 spaces) is being used instead of my setting. No, that's not it. In the course of creating this file, as per your dribble, some "text properties" (deep in the bowels of CC Mode) are being spuriously applied to certain characters in the buffer. I'll track down exactly which keystroke provoked this, and hopefully be able to fix it sometime soonish. Thanks for taking all this trouble to help me reproduce the bug. > Bob -- Alan Mackenzie (Nuremberg, Germany).