From: Daniel Colascione <dancol@dancol.org>
To: turner25@gmail.com, Glenn Morris <rgm@gnu.org>
Cc: 19867@debbugs.gnu.org
Subject: bug#19867: c++-mode indentation issues with C++1x initializer lists
Date: Mon, 16 Feb 2015 13:38:39 -0800 [thread overview]
Message-ID: <54E2635F.2040104@dancol.org> (raw)
In-Reply-To: <CAN1q39WMLXU56_J6DiOsqzhmsi0TSOLOqzJqKEKPbynzSuzTLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On 02/16/2015 11:29 AM, Simon wrote:
> On Mon, Feb 16, 2015 at 2:09 PM, Glenn Morris <rgm@gnu.org> wrote:
>> Simon wrote:
>>
>>> Severity: important
>>
>> Unless it leads to invalid code (eg Python-style languages), I tend to
>> think of indentation bugs as minor problems, since it's just cosmetic.
>> Why do you think this one is important?
>
> I am inclined to follow your lead. C++ code compiles without errors
> as I mentioned.
>
> The bug affects "c++-mode" and since c++-mode mostly (solely?) affects
> cosmetics, then the bug makes c++-mode difficult to use. In fact, I
> have been searching for alternatives, in vain.
>
> I would suggest keeping severity as "important" if this report can be
> assigned more precisely to the "c++-mode" sub-package or group. If
> not, then you may downgrade to "minor" as you said.
OP, your best bet is to dive into cc-engine.el and fix it yourself.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-16 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 17:50 bug#19867: c++-mode indentation issues with C++1x initializer lists Simon
2015-02-16 19:09 ` Glenn Morris
2015-02-16 19:29 ` Simon
2015-02-16 21:38 ` Daniel Colascione [this message]
2015-02-17 19:23 ` Glenn Morris
2015-02-17 19:39 ` Simon
2015-02-16 21:03 ` Daniel Colascione
2020-11-23 14:14 ` Stefan Kangas
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=54E2635F.2040104@dancol.org \
--to=dancol@dancol.org \
--cc=19867@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=turner25@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 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).