Jed

@ssbarnea I think you'd have to come up with a much more formalized specification before anyone can really agree to include anything like this. At this point, there are a...

Yeah. I don't love that this project has variations to minimatch.

That sounds like an excellent solution to me.

Yeah. I think we have to stick to INI syntax.

Another thing we could do is "peek" 👀 into **_extensionless files only_** for a [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) (e.g., `#!/bin/sh`) and treat that particular shebang as an `*.sh` file. That might be a...

We can't just consider the editor, but also the CLI scenario. If I run `editorconfig foo` I should get the same configuration that I would from inside an editor, don't...

Remember that you can change a language from within an editor on the fly, so we need to consider that too.

Basically, in the absence of a `--language` flag, we can defer to some super simple language checks based on peeking certain files or inferring the language from the file extension.

As long as it can be peeked in the first x number of characters in a file, I'm game. Since EditorConfig is run on a file by file basis, I...

See also [vscode | language specific editor settings](https://code.visualstudio.com/updates/v1_10#_language-specific-editor-settings) and [this issue](https://github.com/Microsoft/vscode/issues/51935), which might complicate things a bit. We do, however, have the luxury of giving the last-most rules precedence, because...