summaryrefslogtreecommitdiffhomepage
path: root/bash.html.markdown
diff options
context:
space:
mode:
authorMax Yankov <golergka@gmail.com>2013-08-18 00:59:35 +0200
committerMax Yankov <golergka@gmail.com>2013-08-18 15:03:43 +0200
commit3a88d4f2443c91dba5a968e38ede2b4f145f152a (patch)
tree74c91d785ce80b2122f143da6383fa9f09a1dd85 /bash.html.markdown
parent9a9b5a31e079c635fe4c5afc1127f88fbad091f3 (diff)
Stub bash file
Diffstat (limited to 'bash.html.markdown')
-rw-r--r--bash.html.markdown44
1 files changed, 44 insertions, 0 deletions
diff --git a/bash.html.markdown b/bash.html.markdown
new file mode 100644
index 00000000..ea0a28da
--- /dev/null
+++ b/bash.html.markdown
@@ -0,0 +1,44 @@
+---
+
+language: bash
+contributors:
+ - ["Max Yankov", "https://github.com/golergka"]
+filename: LearnBash.sh
+
+---
+
+Bash is a name of the unix shell, which was also distributed as the shell for the GNU operating system and as default shell on Linux and Mac OS X.
+Nearly all examples below can be a part of a shell script or executed directly in the shell.
+
+[Read more here.](http://www.gnu.org/software/bash/manual/bashref.html)
+
+```bash
+#!/bin/sh
+# First line of the script is shebang which tells the system how to execute the script: http://en.wikipedia.org/wiki/Shebang_(Unix)
+# As you already figured, comments start with #. Shebang is also a comment.
+
+# Simple hello world example:
+echo 'Hello, world!'
+
+# Each command starts on a new line, or after semicolon:
+echo 'This is the first line'; echo 'This is the second line'
+
+# Declaring a variable looks like this:
+VARIABLE="Some string"
+
+# But not like this:
+VARIABLE = "Some string" # Bash will decide that VARIABLE is a command he must execute and give an error because it couldn't be found.
+
+# Using the variable:
+echo $VARIABLE
+echo "$VARIABLE"
+
+# We have the usual if structure:
+if true
+then
+ echo "This is expected"
+else
+ echo "And is was not"
+fi
+
+``` \ No newline at end of file