Modify ↓
Opened 9 years ago
Last modified 9 years ago
#12243 new enhancement
Consider adding an EditorConfig file
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | general | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
If an .editorconfig
file is added in the project, various editors would automatically use the appropriate configuration for file necoding, line endings, indentation etc.
For example in trunk/.editorconfig
:
# See http://EditorConfig.org root = true [*] end_of_line = lf insert_final_newline = true charset = utf-8 [*.py] indent_style = space indent_size = 4 [*.{js,html,yml}] indent_style = space indent_size = 2 [*.css] indent_style = space indent_size = 1 [Makefile] indent_style = tab
Attachments (0)
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Ah, bummer.
Looks like that is discussed in https://github.com/editorconfig/editorconfig/issues/226 as a possible addition.
comment:3 by , 9 years ago
Milestone: | → unscheduled |
---|
We could leave the ticket open and add the .editorconfig
if issue 226 is resolved. Are there any objections besides the issue noted in comment:1?
Note:
See TracTickets
for help on using tickets.
I suggest to close as wontfix. We need
native
for theend_of_line
option. However, the option should set to one of "lf", "cr", or "crlf". See http://editorconfig.org/#supported-properties.