Jorenar

Well, it's still a vast improvement over having a file in home directory, so even if unnecessarily limited, there is still value there.   >having your own project for editor...

>I don't see how EditorConfig is an ideal candidate Because most editors have EC plugins which are capable of setting the settings? As I wrote at the very beginning: _Some...

>Given we try to change the "root"-rule behavior this will introduce a lot of pain because it will negate the fundamental assumption the creator of the root EditorConfig made: that...

Since there aren't any two languages the names of which differ only by letters case (and hopefully there never be such situation), would just converting all letters to lowercase be...

I confirm: either code is wrong or documentation needs to be changed to show parameter taking a function instead of string

I'm not even sure how I let that typo get there, but the fix is to replace `-s` with `-S` in line 13

@hsanson Indeed, version 1.7.6 (2016-09-09) doesn't have `-S` option, which was added in version 1.7.7 (2022-10-17). I'll add a check to test `-S` option availability.

One way to fix that would be to add those arguments unconditionally: ```vim return '%e -analyze %s' \ . ' --extra-arg=-Xclang --extra-arg=-analyzer-output=text --extra-arg=-fno-color-diagnostics' \ . ale#Pad(l:user_options) \ . (!empty(l:build_dir) ?...

> I think this issue was more about being able to jump to location in other files and running language server diagnostics for an entire workspace. @w0rp @hsanson So that...

@dileepfrog Hi! Since it was quite few years since the issue was reported and (potentially) related #2442 was long resolved, could you please verify if the problem still occurs?