Defaults taken from kde coding style.
This file enables a minimum style guide to be enforced across editors,
like line endings, character encoding, tabs vs spaces, indent size
and some more.
https://editorconfig.org/
Details
Details
- Reviewers
hindenburg tcanabrava gszymaszek - Commits
- R319:7907b7a88fd3: Add editorconfig
Diff Detail
Diff Detail
- Repository
- R319 Konsole
- Branch
- add-editorconfig
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 2970 Build 2988: arc lint + arc unit
| .editorconfig | ||
|---|---|---|
| 5 | https://community.kde.org/Policies/Kdelibs_Coding_Style this style guide does not differentiate between different file types, note specific rules for specific file types can easily be added. | |
| 11 | This is a recommendation and most editors do not enforce it. | |
| 16 | This has to do with markdown and the way it handles line breaks. | |
Comment Actions
I think the idea in general is good. +1 from my side, things can still be improved later if it turns out that it does not work.
PS: indeed, we do not have a hard word wrap for the line length. Maybe remove this line :)
PPS: alternatively, one could add a .kateconfig file. Kate supports .editor config as well, though.
Comment Actions
PPS: alternatively, one could add a .kateconfig file. Kate supports .editor config as well, though.
That would defeat the purpose of this, this file is about making collaborative project editing easier. Not every developer uses kate. Actually the opposite, In the last stackoverflow survey it didn't even make the 0.2% mark for desktop developers: https://insights.stackoverflow.com/survey/2017#technology-most-popular-developer-environments-by-occupation.
Comment Actions
@hindenburg I see no blocker for this, excluding maybe line length, yet that is as the comment says more a suggestion than a hard limit.
Comment Actions
I'm not against this per se but why does every application need this in its source folder?
For reference: https://editorconfig.org/
Comment Actions
Like most other editors, have something in ~; this would be ~/.editorconfig
? Again that defeats the purpose of this thing. The whole point is that different projects can have different styles and that your editor does not impose its settings on the project, your development environment should pick up the project settings. What you suggest is bit like suggestion a global package.json for all npm projects.
Comment Actions
I second @lbergdoll , Different projects have different setups (like tabs vs spaces), having this file on the repository would help people that don't know the code style to have a head start.
| .editorconfig | ||
|---|---|---|
| 2 | https, please 🙂 | |
| 15 | I think it’s better to suggest some line length limit in Markdown files as well, as it makes these files readable in plain text (incapable of Markdown previewing or of text soft wrapping, like mcedit) editors. Like it’s in cgit/syntax-highlighting/tree/README.md | |
| 19 | Is it really a good idea? | |