From: Giuseppe Bilotta Date: Mon, 29 Nov 2010 14:47:50 GMT Subject: [PATCH 1/6] CodingGuidelines: mention whitespace preferences for shell scripts Message-ID: <1291042075-19983-2-git-send-email-giuseppe.bilotta@gmail.com> In-Reply-To: <1291042075-19983-1-git-send-email-giuseppe.bilotta@gmail.com> Signed-off-by: Giuseppe Bilotta --- Documentation/CodingGuidelines | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 5aa2d34..7ecce51 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -31,6 +31,12 @@ But if you must have a list of rules, here they are. For shell scripts specifically (not exhaustive): + - We use tabs for indentation. + + - The choices in case ... esac statement are not indented with respect + to the the case and esac lines. The body of the choices however _is_ + indented (by one tab). + - We prefer $( ... ) for command substitution; unlike ``, it properly nests. It should have been the way Bourne spelled it from day one, but unfortunately isn't. -- 1.7.3.2.624.gec6c7.dirty