summaryrefslogtreecommitdiff
path: root/gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl')
-rw-r--r--gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl10
1 files changed, 4 insertions, 6 deletions
diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl b/gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl
index 32e255f3..ff2c5fee 100644
--- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl
+++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.gmi.tpl
@@ -2,6 +2,10 @@
> Published at 2021-05-16T14:51:57+01:00
+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.
+
+=> https://google.github.io/styleguide/shellguide.html Google Shell Style Guide
+
```
.---------------------------.
/,--..---..---..---..---..--. `.
@@ -17,12 +21,6 @@
<< template::inline::toc
-## Introduction
-
-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.
-
-=> https://google.github.io/styleguide/shellguide.html Google Shell Style Guide
-
## My modifications
These are my modifications to the Google Guide.