Added a small section addressing empty editorconfig files

[mipo256]

Closes #86

CC: @xuhdev

---

📚 Documentation preview 📚: https://editorconfig-specification--87.org.readthedocs.build/

[cxw42]

This is a different topic than "empty editorconfig files." Would you please move it to a separate PR? That would make the git history cleaner, and this PR more focused. Thanks!

[mipo256]

Fully agree. I can move it into a separate "polishing" commit. What are you thoughts on this, @cxw42 ?

CC: @xuhdev

[cxw42]

Actually, now that I think about it more, I believe this should stay as it was. "Section name" is defined above (here). Using the term in this paragraph is therefore unambiguous.

Consider the section name [{*.txt,*.md}]. At the command prompt, I would think of that as two "glob expression"s (*.txt and *.md). However, in this paragraph the whole name {...} is taken as a unit. I worry that if we made this change it might confuse readers. Sorry for the late change!

[cxw42]

@mipo256 Apologies for the confusion --- I hit Submit too soon. Please see #87 (comment) . I thought about it some more and realized I think "section name" should stay as it is --- details in that comment. Thanks!

[mipo256]

I agree with you, @cxw42. I think it makes sense to retain the "section name" change to retain as it is.

However, the section name, as I see it, is a single glob expression, that contains the multiple parts, like the following: [a-zA-Z0-9]{4} - it is a single regexp, that contains a character group and a quantifier. So I think:

At the command prompt, I would think of that as two "glob expression"s (*.txt and *.md)

It is not fully accurate, these are parts of a single glob (I might be wrong, but this is as far as I see it).

But at the end of the day, I see your suggestion as a good way to go. I rolled back the change.

[mipo256]

FTR: I'll squash the commits before merge, do not worry.

CC: @cxw42 @xuhdev

[cxw42]

@mipo256 thanks! Yes, I agree the phrase "glob expression" could be interpreted multiple ways.