Results 64 comments of Jorenar

Eugene wants Uncrustify to apply this style: ``` void (*foo)() = func; // star to name int* x; // star to type ``` Currently, if they configure `type* name`, then...

Could this be somewhat related to #3252?

@gpncarl Would you be interested in sending a PR with your changes?

Let's consider an example: You work on a C++ project. As it is a well maintained repository, it does specify `root=true` in the root of the repository. There are **no...

>A particular editor's default configuration is outside the scope of EditorConfig. Not one particular editor - I want to have one common default config for **every** editor I use. >Create...

``` BigProject ├── build │   └── deps │   ├── foo.d │   └── bar.d ├── .editorconfig ├── Makefile ├── subprojects │   └── parallel_project │   ├── build │ ├── .editorconfig │ ├──...

How about two environment variables? It covers both use-cases, doesn't really require more work to implement, is pretty clear what effect it has and the user will need to make...

>I agree with this. Overriding a root=true project's settings defeats the purpose of editorconfig. The settings set in `root=true` file still ought to take precedence over the `$EDITORCONFIG_SUPERROOT`. The variable...

`$EDITORCONFIG_SUPERROOT`: ``` [Makefile] indent_style = tab [*.py] indent_style = space indent_size = 4 [*.c] indent_size = 4 [*.rb] indent_style = tab ``` `project/.editorconfig`: ``` root=true [*.c] indent_style = space indent_size...

Currently the it looks like this: * `~/.vimrc` * `project/.editorconfig` * `project/subdir/.editorconfig` * `project/extern/.editorconfig` `.vimrc` is already ignoring the `root=true`! With the variables: * `~/.vimrc` * `$EDITORCONFIG_SUPERROOT` * `project/.editorconfig` *...