Most plugin adopt the second option for indent_style (only convert tab/spaces in modified lines, do not touch non-modified lines) But we really have other options.Īctually this is also a more general problem of editorconfig, and it's the root of some issues in the repo. It seems you against max_empty_lines because you only consider the third option. Silently trim extra empty lines on save.Do not allow enter extra empty lines, and/or when a line is modified, collapse the adjacent empty lines, but do not touch non-modified lines.
Three, for those allow "empty lines in multiline string", some team adopt the coding style that also restrict it and force the programmers use escape (like \n), placeholder (like $NEWLINE) or other form (string concat, etc.) instead of rely on error-prone multiple empty lines. For example many C-family languages require \ at the end of each line of multiline strings. Two, many languages do not have "empty lines in multiline string" problem because they do not have multiline strings, or they do not allow empty lines in multiline strings. For example, ESLint no-multiple-empty-lines rule you mentioned also apply to multiline comments. So let me try again.įirst, "empty lines in multiline comments" is not a problem.