Add .editorconfig and revise doc files with style#1808
Merged
jimklimov merged 12 commits intonetworkupstools:masterfrom Jan 14, 2023
Merged
Add .editorconfig and revise doc files with style#1808jimklimov merged 12 commits intonetworkupstools:masterfrom
jimklimov merged 12 commits intonetworkupstools:masterfrom
Conversation
jimklimov
added
documentation
CI
…d for block-comment definitions) [networkupstools#894]
…er [networkupstools#894]" This reverts commit f9b195a4650766ef81cc4daa35f2d6cee932c87a.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While not a full-fledged solution to #894 goals, this is a first step allows many editors and IDEs to save consistent representation/markup of the codebase. For a practical test-drive, text files were edited to drop trailing whitespaces (also testing exceptions by filenames) and wrap lines too long. Bits of docs were refreshed along the way.
At this time there is no special automation involved to check/enforce this style setting (like there would be with
clang-format). However if there are "offences" in some codebase parts, it should hopefully "converge" to some one standard over time as those files get edited and saved by cooperating tools.