emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#14008: closed (Better autoindent for C++11 code?)


From: GNU bug Tracking System
Subject: bug#14008: closed (Better autoindent for C++11 code?)
Date: Thu, 07 Nov 2019 23:42:01 +0000

Your message dated Fri, 08 Nov 2019 00:41:21 +0100
with message-id <address@hidden>
and subject line Re: bug#14008: Better autoindent for C++11 code?
has caused the debbugs.gnu.org bug report #14008,
regarding Better autoindent for C++11 code?
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
14008: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14008
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Better autoindent for C++11 code? Date: Wed, 20 Mar 2013 11:38:58 -0400
C++11 introduced lambda syntax []() { ... } and other strange things that Emacs indents strangely.

for_each(range.begin(), range.end(), [=](int i) {
    cout << strings[i] << endl;
  });

I would like the final line `});` to have the same indentation level as the first line `for_each...`.

Here's another example:

for_each(range.begin(), range.end(), [&](int i) {
             std::async(
                        launch::async,
                        [&]() { strings[i] = fizzy(i); }
                        );
  });

The arguments to std::async and its closing parenthesis are indented much too far; I would like them indented only one level further than where std::async is itself indented. Any tips for achieving this?

--
Cheers,

Andrew Pennebaker
www.yellosoft.us

--- End Message ---
--- Begin Message --- Subject: Re: bug#14008: Better autoindent for C++11 code? Date: Fri, 08 Nov 2019 00:41:21 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
Alan Mackenzie <address@hidden> writes:

>> Do you think there is anything more to do here, or should this bug be
>> closed?
>
> I think the bug should now be closed.

Thanks, I'm therefore closing this bug now.

Best regards,
Stefan Kangas


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]