aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKate Ward <kate.ward@forestent.com>2020-04-09 17:55:20 +0200
committerKate Ward <kate.ward@forestent.com>2020-04-09 17:55:20 +0200
commitfb1f0537ec1fdb592c133327969f73334aabbeb0 (patch)
tree639298c4a9b969be2f80e601152d2195e6a7e990
parent7cafbef7743c487216a619c1fcb2a34b60a7e7e2 (diff)
downloadshflags-fb1f0537ec1fdb592c133327969f73334aabbeb0.tar.gz
Removed line limit restrictions.
-rw-r--r--CONTRIBUTING.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9915b70..cfc4918 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -16,7 +16,7 @@ doSomething() {
}
```
-One-line functions are allowed if they can fit within the 80 char line limit.
+One-line functions are allowed if they are for a single command.
```sh
doSomething() { echo 'done!'; }
@@ -118,10 +118,11 @@ if [ -z 'some string' ]; then
fi
```
-Lines of code should be no longer than 80 characters unless absolutely
-necessary. When lines are wrapped using the backslash character '\', subsequent
-lines should be indented with four (4) spaces so as to differentiate from the
-standard spacing of two characters, and tabs may not be used.
+Lines of code have no line limit, although the general preference is to wrap
+lines at reasonable boundaries (e.g., between if/then/else clauses). When long
+lines are wrapped using the backslash character '\', subsequent lines should be
+indented with four (4) spaces so as to differentiate from the standard spacing
+of two characters, and tabs may not be used.
```sh
for x in some set of very long set of arguments that make for a very long \