From: Alan Mackenzie <acm@muc.de>
To: Kevin Yu <yujie052@gmail.com>
Cc: bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: C++-mode, wrong indentation
Date: Wed, 2 Jul 2008 09:57:31 +0000 [thread overview]
Message-ID: <20080702095731.GA2594@muc.de> (raw)
In-Reply-To: <42b562540807012159jc4c246bg1fcbe8e9e2ea2ac6@mail.gmail.com>
Hi, Kevin!
On Wed, Jul 02, 2008 at 12:59:36PM +0800, Kevin Yu wrote:
> Hi,
> ====code====
> if (x < 0 || y < 0 || x >= 9) {
> // c++-mode will indent this line with
> 2*c-basic-offset when editing.
> } // and this line with c-basic-offset
> ====code====
> If you copy the above code into a c++-mode buffer, the indentation is
> right. But when you reenter the ">=" of first line, the indentation
> goes wrong again.
Yes. This is a bug.
If you're interested in what's happening, (you don't have to be ;-):
#########################################################################
The problem is to do with CC Mode's suboptimal handling of templates in
C++ Mode and Java Mode.
If you delete the ">=", then type just the ">" (as a first step towards
typing ">="), CC Mode spuriously recognises the "<..>" pair as template
brackets. You can see this with show-paren-mode, or C-M-p.
When you then type the "=", it leaves the "<" as a bracket, but not the
">". This messes up the paren matching, and causes mis-analysis of the
following lines of code.
#########################################################################
I can probably fix this quite easily.
Many thanks for a crisp, high quality bug report!
> Best regards
> Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-07-02 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 4:59 C++-mode, wrong indentation Kevin Yu
2008-07-02 9:57 ` Alan Mackenzie [this message]
2008-07-14 13:44 ` Alan Mackenzie
2010-02-04 21:24 ` Alan Mackenzie
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=20080702095731.GA2594@muc.de \
--to=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yujie052@gmail.com \
/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.