From 89f83d49ad7d4cd8baa815993d3172ca72e5b30e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sat, 8 Apr 2023 12:32:25 +0300 Subject: Update content for html --- .../2021-05-16-personal-bash-coding-style-guide.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'gemfeed/2021-05-16-personal-bash-coding-style-guide.html') diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.html b/gemfeed/2021-05-16-personal-bash-coding-style-guide.html index 499d4cc7..861e9256 100644 --- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.html +++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.html @@ -10,7 +10,7 @@

Personal Bash coding style guide



-Published at 2021-05-16T14:51:57+01:00
+Published at 2021-05-16T14:51:57+01:00

    .---------------------------.
@@ -27,7 +27,7 @@
 

 Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. 

 

-Google Shell Style Guide

+Google Shell Style Guide

 

 
My modifications


 

@@ -379,27 +379,27 @@ fi
 

 The following two paragraphs are thoroughly quoted from the Google guidelines. But they hit the hammer on the head:

 

-If you are editing code, take a few minutes to look at the code around you and determine its style. If they use spaces around their if clauses, you should, too. If their comments have little boxes of stars around them, make your comments have little boxes of stars around them too.

+If you are editing code, take a few minutes to look at the code around you and determine its style. If they use spaces around their if clauses, you should, too. If their comments have little boxes of stars around them, make your comments have little boxes of stars around them too.

 

-The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what you are saying rather than on how you are saying it. We present global style rules here, so people know the vocabulary. But local style is also important. If the code you add to a file looks drastically different from the existing code around it, the discontinuity throws readers out of their rhythm when they go to read it. Try to avoid this.

+The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what you are saying rather than on how you are saying it. We present global style rules here, so people know the vocabulary. But local style is also important. If the code you add to a file looks drastically different from the existing code around it, the discontinuity throws readers out of their rhythm when they go to read it. Try to avoid this.

 

 

 
Advanced Bash learning pro tip


 

 I also highly recommend having a read through the "Advanced Bash-Scripting Guide" (not from Google). I use it as the universal Bash reference and learn something new every time I look at it.

 

-Advanced Bash-Scripting Guide

+Advanced Bash-Scripting Guide

 

 Other related posts are:

 

-2022-01-01 Bash Golf Part 2

-2021-11-29 Bash Golf Part 1

-2021-06-05 Gemtexter - One Bash script to rule it all

-2021-05-16 Personal Bash coding style guide (You are currently reading this)

+2022-01-01 Bash Golf Part 2

+2021-11-29 Bash Golf Part 1

+2021-06-05 Gemtexter - One Bash script to rule it all

+2021-05-16 Personal Bash coding style guide (You are currently reading this)

 

 E-Mail your comments to hi@paul.cyou :-)

 

-Back to the main site

+Back to the main site

 

 Generated with Gemtexter |
 served by OpenBSD/httpd(8) |
-- 
cgit v1.2.3