From: Lars Ingebrigtsen <larsi@gnus.org>
To: ar <ar123456@gmail.com>
Cc: 48877@debbugs.gnu.org
Subject: bug#48877: emacs 26.x incorrect enum indentation for c++
Date: Mon, 07 Jun 2021 11:45:04 +0200 [thread overview]
Message-ID: <87y2bmovof.fsf@gnus.org> (raw)
In-Reply-To: <CA+fXA1AS2_vaFyW+WOBX=5Kv1JnrwggNkRKyHk2ffDgMRZodaw@mail.gmail.com> (ar's message of "Sun, 6 Jun 2021 09:45:00 -0400")
ar <ar123456@gmail.com> writes:
> This is happening even if I run 'emacs -Q':
>
> class A {
> public:
> enum EnumWithLongName {
> val0,
> val1,
> val2
> };
> };
I can reproduce this in Emacs 26, but it's been fixed in Emacs 28.
Therefore I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-06-07 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 13:45 bug#48877: emacs 26.x incorrect enum indentation for c++ ar
2021-06-07 9:45 ` Lars Ingebrigtsen [this message]
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=87y2bmovof.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48877@debbugs.gnu.org \
--cc=ar123456@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).