Message ID | 20221011152232.25280-1-paren@disroot.org |
---|---|
State | New |
Headers | show |
Series | Add EditorConfig specification. | expand |
Context | Check | Description |
---|---|---|
cbaines/comparison | success | View comparision |
cbaines/git-branch | success | View Git branch |
cbaines/applying patch | success | View Laminar job |
cbaines/issue | success | View issue |
Hi! "( via Guix-patches" via 写道: > * .editorconfig: New file. All these values LGTM, but I use the correct editor. > max_line_length = 85 As discussed on IRC, it's obvious to ‘us’ what this really means, but I wonder if it's universal. Unless someone disagrees, I think it's OK. Kind regards, T G-R
Am Dienstag, dem 11.10.2022 um 17:59 +0200 schrieb Tobias Geerinckx- Rice: > Hi! > > "( via Guix-patches" via 写道: > > * .editorconfig: New file. > > All these values LGTM, but I use the correct editor. > > > max_line_length = 85 > > As discussed on IRC, it's obvious to ‘us’ what this really means, > but I wonder if it's universal. Unless someone disagrees, I think > it's OK. If I recall correctly, the correct editor uses 79 as fill-column. Even if extended URLs are nasty in other editors, as discussed in IRC, I'd claim that to be "a good thing", because the failed word-wrapping shows the writer how nasty that'd be and makes them use string-append. Cheers
diff --git a/.editorconfig b/.editorconfig new file mode 100644 index 0000000000..bc68ff24c8 --- /dev/null +++ b/.editorconfig @@ -0,0 +1,16 @@ +root = true + +[*.{c,h,cpp,hpp,el,scm,ac,am,m4,po}{,.in}] +end_of_line = lf +insert_final_newline = true +charset = utf-8 +trim_trailing_whitespace = true + +[*.{c,h,cpp,hpp,ac,am,m4,el,scm}{,.in}] +max_line_length = 85 + +[*.{c,h,cpp,hpp,ac,m4,el,scm}{,.in}] +indent_style = space + +[*.{c,h,cpp,hpp}{,.in}] +indent_size = 4