From: Stefan Kangas <stefan@marxist.se>
To: 26674@debbugs.gnu.org
Subject: bug#26674: [Stefan Kangas] Re: bug#26674: 24.3; Inconsistent indentation in C++ mode initialization lists
Date: Thu, 22 Oct 2020 18:48:39 -0700 [thread overview]
Message-ID: <CADwFkmmM6gKFpbWhmwwcpNTzE6_G-9ZBRRPbs=af2vZFeeu+Cg@mail.gmail.com> (raw)
In-Reply-To: <CAHWYW93=mR_mKCn5RQkxGmpAWaCtB1PviNy1dDsreacL1_kwUg@mail.gmail.com>
[ Forwarding to the bug tracker since I forgot to include it in Cc. ]
-------------------- Start of forwarded message --------------------
From: Stefan Kangas <stefan@marxist.se>
To: Greg Long <gregory.g.long@gmail.com>
Subject: Re: bug#26674: 24.3; Inconsistent indentation in C++ mode
initialization lists
Date: Mon, 10 Aug 2020 13:44:18 -0700
Greg Long <gregory.g.long@gmail.com> writes:
> When creating an initialization list for a constructor in C++ mode there
> is an inconsistency in indentation. In the following code:
>
> foo::foo()
> : m_test_var0(100)
> , m_test_var1(100)
> , m_test_var2(100)
> , m_test_var3(100)
> , m_test_var4(100)
> , m_test_var5(100)
> , m_test_var6(100)
> , m_test_var7(100)
> , m_test_var8(100)
> , m_test_var9(100)
> , m_test_var10(100)
> , m_test_var11(100)
> , m_test_var12(100)
> , m_test_var13(100)
> , m_test_var14(100)
> , m_test_var15(100)
> , m_test_var16(100)
> , m_test_var17(100)
> , m_test_var18(100)
> , m_test_var19(100)
> , m_test_var20(100)
> , m_test_var21(100)
> , m_test_var22(100)
> , m_test_var23(100)
> , m_test_var24(100)
> , m_test_var25(100)
> , m_test_var26(100)
> {}
>
> variables inserted before m_test_var25 are not indented, while
> ones after m_test_var25 are indented (in the same style as m_test_var26). The
> indentation doesn't always happen after exactly 26 variables and the
> size of indentation is not always 2 spaces, instead the
> behavior seems to depend on the length of the variable strings. However
> the indentation will always happen eventually. It appears the actual
> values within the parentheses don't matter, either.
I can't reproduce this on current master. Are you still seeing this
using a recent version of Emacs?
If I don't hear back from you within a couple of weeks, I'll just
close this bug as unreproducible.
Best regards,
Stefan Kangas
-------------------- End of forwarded message --------------------
next prev parent reply other threads:[~2020-10-23 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADwFkmnMXx9OUKL3+RQq0wcSsnkdgfxjZpn24cV=evqiSEt+Pg@mail.gmail.com>
2017-04-27 0:32 ` bug#26674: 24.3; Inconsistent indentation in C++ mode initialization lists Greg Long
2020-10-23 1:48 ` Stefan Kangas [this message]
2020-10-23 1:58 ` bug#26674: [Stefan Kangas] " 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='CADwFkmmM6gKFpbWhmwwcpNTzE6_G-9ZBRRPbs=af2vZFeeu+Cg@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=26674@debbugs.gnu.org \
/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).