| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
* Without this, editors like Sublime or Atom when using an EditorConfig
plugin, they will change e.g. two spaces in a commit message (such
as the second line in a bullet list item) to a tab upon saving
the commit message.
Change-Id: Ie0c5e1fcfe7853a737c1ccf1880052660f4171e2
|
|
|
|
|
|
|
|
|
| |
When working on patch Ib90c74de1a153b6a01c3 I found that when using
Atom or Sublime with editorconfig enabled, a line break after
`* foo\n bar` in a markdown file would often produce a tab instead
of two spaces for the third line.
Change-Id: I0ace4e675a20020a362ac3f29f8c1d8f61a99e1c
|
|
|
|
|
|
|
|
|
| |
YAML files may be invalid if the indentation is done with tabs.
To prevent this from happening, configure developer's IDE's to
use spaces on these types of files.
Bug: T253594
Change-Id: I0c49c2b476a49508ea1036c1bd71e7de83dbf8b0
|
|
|
|
|
|
|
|
|
| |
See https://www.mediawiki.org/wiki/Manual:Coding_conventions#Tab_size
This is a follow-up on I8e776665dca255ff5dead1a9874bcd73344e4d20
Bug: T172959
Change-Id: Ifc7ef5e3a095db505bbbff4c09c87213ae7259aa
|
|
.editorconfig <http://editorconfig.org/> is a standardized format
that many IDEs support (or have plugins for) to use a project's code
style by default.
Bug: T172959
Change-Id: I8e776665dca255ff5dead1a9874bcd73344e4d20
|