File tree 2 files changed +12
-8
lines changed
2 files changed +12
-8
lines changed Original file line number Diff line number Diff line change 21
21
copyright = '2019--2024, EditorConfig Team'
22
22
author = 'EditorConfig Team'
23
23
24
- version = '0.16.0 '
25
- release = '0.16.0 '
24
+ version = '0.16.1 '
25
+ release = '0.16.1 '
26
26
27
27
# -- General configuration ---------------------------------------------------
28
28
Original file line number Diff line number Diff line change 1
- .. Copyright (c) 2019--2020 EditorConfig Team
1
+ .. Copyright (c) 2019--2024 EditorConfig Team
2
2
All rights reserved.
3
3
4
4
Redistribution and use in source and binary forms, with or without
@@ -73,15 +73,19 @@ EditorConfig organization.
73
73
File Format
74
74
===========
75
75
76
+ .. versionchanged :: 0.16.1
77
+
76
78
EditorConfig files are in an INI-like file format.
77
- In an EditorConfig file, all beginning whitespace on each line is considered
78
- irrelevant. Each line must be one of the following:
79
+ To read an EditorConfig file, take one line at a time. For each line:
80
+
81
+ #. Strip all leading and trailing whitespace
82
+ #. If the remaining text is not empty, process the text as specified for its
83
+ type below.
84
+
85
+ The types of lines are:
79
86
80
- - Blank: contains only whitespace characters.
81
87
- Comment: starts with a ``; `` or a ``# ``.
82
88
- Section Header: starts with a ``[ `` and ends with a ``] ``.
83
- - May not use any non-whitespace characters outside of the surrounding
84
- brackets.
85
89
- May contain any characters between the square brackets (e.g.,
86
90
``[ `` and ``] `` and even spaces and tabs are allowed).
87
91
- Forward slashes (``/ ``) are used as path separators.
You can’t perform that action at this time.
0 commit comments