mirror of
https://forge.sourceware.org/marek/gcc.git
synced 2026-02-22 03:47:02 -05:00
2c605367b4
According to the editorconfig file format description, a match against
one of multiple different strings is described with those different
strings separated by commas and within curly braces. E.g.
[{x,y}.txt]
https://editorconfig.org/, under "Wildcard Patterns".
The current libstdc++-v3/.editorconfig file has a few places where we
match against similar globs by using strings separated by commas but
without the curly braces. E.g.
[*.h,*.cc]
This doesn't take affect in neovim nor emacs (as far as I can tell), I
haven't looked into other editors.
I would expect that following the standard syntax described in the
documentation would satisfy more editors. Hence this patch suggests
following that standard by using something like:
[*.{h,cc}]
libstdc++-v3/ChangeLog:
* .editorconfig: Adjust globbing style to standard syntax.
Signed-off-by: Matthew Malcomson <mmalcomson@nvidia.com>
39 lines
593 B
INI
39 lines
593 B
INI
# top-most EditorConfig file for libstdc++-v3
|
|
root = true
|
|
|
|
[*]
|
|
end_of_line = lf
|
|
insert_final_newline = true
|
|
|
|
[*.{h,cc}]
|
|
charset = utf-8
|
|
indent_style = tab
|
|
indent_size = 2
|
|
tab_width = 8
|
|
trim_trailing_whitespace = true
|
|
|
|
[{Makefile,ChangeLog}*]
|
|
indent_style = tab
|
|
indent_size = 8
|
|
trim_trailing_whitespace = true
|
|
|
|
[ChangeLog*]
|
|
charset = utf-8
|
|
|
|
[*.xml]
|
|
charset = utf-8
|
|
indent_size = 2
|
|
tab_width = 8
|
|
trim_trailing_whitespace = true
|
|
|
|
[*.py]
|
|
indent_style = space
|
|
indent_size = 4
|
|
trim_trailing_whitespace = true
|
|
|
|
[*.exp]
|
|
indent_style = tab
|
|
indent_size = 4
|
|
tab_width = 8
|
|
trim_trailing_whitespace = true
|