-
Uncrusify gets confused with #if macros disabling part of an if statement inside a case statement, eg:
```
case 0: {
#if TARGET_A
if (flags & 1) {
…
-
# Description
The [language-cpp14](https://atom.io/packages/language-cpp14) package provides a grammar called ‘C++14’. When a C++ header file is open and set to C++14, running the beautifier causes U…
-
[//]: # " If the issue is connected to existing Uncrustify options please, if possible, add the"
[//]: # " following information to ease up the process:"
[//]: # " • a link to a debug file:"
[//…
-
Have you thought about using a code formatter like [astyle](http://astyle.sourceforge.net/) or [uncrustify](https://github.com/uncrustify/uncrustify)? It's good to have a consistent style.
Rubo3 updated
2 years ago
-
[//]: # " generated with: 'uncrustify -p debug.txt -c pathToUsedConfig.cfg -f toBeFormatedFile.cpp' "
[//]: # " Example: [debug.txt](https://linkToTheFile)"
[//]: # " Example ho…
-
[//]: # " If the issue is connected to existing Uncrustify options please, if possible, add the"
[//]: # " following information to ease up the process:"
[//]: # " • a link to a debug file:"
[//…
-
Project needs a linter/beautifier, would be helpful instead of manually having to ensure style compliance.
Possible options include:
- [Artistic Style](http://astyle.sourceforge.net/)
- [Uncrust…
-
I think we do not need the paren on `return` statements. i would add this option to uncrustify.cfg:
``` bash
mod_paren_on_return = remove
```
what do you think?
-
For instance, if you select multiple files or groups in Project Navigator and select an option in the Uncrustifier menu bar option "Format Selected Files".
Selecting a top level group and hitting "…
-
Our code style is quit literally **COMPLETELY RANDOM**.
Maybe not random, probably has to do something with the age of the code.
A excerpt from https://github.com/libevent/libevent/pull/282 code re…