New CLion 1.1 EAP: Select and Use Your Favorite Code Style

Anastasia Kazakova

Hi all,

A preview build for CLion 1.1 (141.2144) is now available for download. Patch update is available from CLion 1.1 first EAP build.

The first EAP delivered many new code style options to reflect your desired guidelines more precisely. With this new build, we are offering something even more impressive!

While configuring a code style scheme for your projects, you can now apply settings from one or several well-known guidelines:

Please note that the last three options include only the braces placement rules.

To apply these styles, go to Editor | Code Style | C/C++ settings, find the Set from… option on the right-hand side of the window and select the preferred guideline scheme there:
predefined_style
Changes will be highlighted in the preview window and a Reset option will appear. (There’s a small issue with it right now – Reset doesn’t appear immediately, but any action in the settings windows triggers the proper event.)

This build also addresses an unpleasant bug in the debugger with the option “Hide out of scope values” which also hides this pointer in Variables and Watches views. Find tge full list of fixes in our tracker. Download the EAP build now and give it a try!

Happy developing!

Your CLion Team

Comments below can no longer be edited.

17 Responses to New CLion 1.1 EAP: Select and Use Your Favorite Code Style

  1. cossio says:

    July 24, 2015

    Are you planning to support C++14 in the editor? (Currently, v1.0.5, some C++14 code compiles, but the syntax highlighter highlights fake errors). When?

    • Anastasia Kazakova says:

      July 25, 2015

      Yes, we do plan. You can upvote and follow this: https://youtrack.jetbrains.com/issue/CPP-1263 to get the updates. No exact estimation are clear for now. Won’t be done prior to 1.1 for sure.

  2. David Zemon says:

    July 25, 2015

    Good job guys! The new formatter is excellent! And finally, I can indent visibility keywords and members independently! 😀

    • Anastasia Kazakova says:

      July 25, 2015

      Thanks!

  3. wl.nicholas says:

    July 25, 2015

    For people who are working with the google code style, here’s a plugin to run cpplint.py on the fly.

  4. Anton says:

    July 25, 2015

    Please, add an option to use lowercase characters in the filename, independent from the classname (I’m talking about a new calss dialog). Linux filesystems are case sensitive.
    https://youtrack.jetbrains.com/issue/CPP-2747

  5. jh says:

    July 26, 2015

    Please add an option to view variable values in hexadecimal format. It’s very useful when handling with pointers.

  6. jh says:

    July 26, 2015

    Would you please support Adobe’s Source Code Pro font in all IntelliJ products? Currently its bold font makes the whole string unreadable.

  7. jh says:

    July 27, 2015

    Build 141.2144 failed to debug with bundled llvm: step forward at the breakpoint will cause the debugger hung.

    • Anastasia Kazakova says:

      July 27, 2015

      Could you please share a sample project or at least a debug log – collect debug logs (Help | Configure Debug Log | Add #com.jetbrains.cidr.execution.debugger) while starting a session and send to us (logs can be found in Help | Show Log) to clion-support at jetbrains.com. We’ll have a look at what’s going on there.

  8. Sunny says:

    August 2, 2015

    Hey Anastasia?

    Any news on this bug?

    http://gyazo.com/5af41a219a1d9edd01656fd9d16a5a74

    https://gyazo.com/5f149f8ed5b38e07f6b1b52c7ecbd267

    Every time I take a user input, it prints the user input that it just got, then executes the next statement

    • Anastasia Kazakova says:

      August 2, 2015

      What OS is that?
      If it’s Widows, MinGW than it could be related to https://youtrack.jetbrains.com/issue/CPP-2580

      • Sunny says:

        August 2, 2015

        Sorry Anastasia, i forgot to mention.
        Its Windows 10, Min-GW w64.

        • Anastasia Kazakova says:

          August 2, 2015

          Than it’s really looks connected to the issue I’ve mentioned. Could you please add your screenshots in comments there? You can also follow the ticket to get the updates.

Subscribe

Subscribe for updates