specification
specification copied to clipboard
editorconfig
Specification of EditorConfig file format
It looks like the current wording still leads to too much confusion: https://github.com/editorconfig/specification/pull/29#discussion_r783382976 I therefore propose to remove the explaining addition about inline comments at all, in favor of a...
The specification contains the following language: > Inserting a `#` or `;` after non-whitespace characters in a line (i.e., inline) shall neither be parsed as a comment nor as part...
The text at the aforementioned point reads: > **`root`**: special property that should be specified at the top of the file outside of any sections. Set to "true" to stop...
max_line_length is used in this repo, in various plugins and core. Is there any reason why this specification doesn't describe it?
See the confusion in https://github.com/editorconfig/editorconfig-core-test/issues/37#issuecomment-614380017
POSIX requires non-empty files to feature a final end of line (e.g. `\n` line feed) terminator, and in general EditorConfig does a good job of helping users to enforce this....
This issue is opened to discuss the table of content for the specification. Here is a first shot: ## Introduction Introduction of the specification. ## File Format Describes the file...
* Section names can have trailing whitespace (the core tests expressly check this). * When deciding what kind of line we have, all leading whitespace is ignored, and the trailing...
**Note:** This PR builds on #46. Please review **only** the head commit. All other commits are part of #46. Part of https://github.com/editorconfig/editorconfig/issues/496 . Update the spec to expressly permit the...
Taking the specification literally, the glob `*.py` would not match `foo/bar.py` since `foo/bar` includes the slash character. The C library for editorconfig adds `**/` to the start of the glob...
