2013-08-18 02:59:35 +04:00
|
|
|
|
---
|
2024-10-21 01:11:09 +03:00
|
|
|
|
language: Bash
|
2013-08-18 02:59:35 +04:00
|
|
|
|
contributors:
|
2013-08-19 20:14:02 +04:00
|
|
|
|
- ["Max Yankov", "https://github.com/golergka"]
|
|
|
|
|
- ["Darren Lin", "https://github.com/CogBear"]
|
2013-09-22 08:06:35 +04:00
|
|
|
|
- ["Alexandre Medeiros", "http://alemedeiros.sdf.org"]
|
2013-12-18 12:37:27 +04:00
|
|
|
|
- ["Denis Arh", "https://github.com/darh"]
|
2014-07-23 10:43:18 +04:00
|
|
|
|
- ["akirahirose", "https://twitter.com/akirahirose"]
|
2014-08-06 22:30:15 +04:00
|
|
|
|
- ["Anton Strömkvist", "http://lutic.org/"]
|
2014-09-06 05:51:48 +04:00
|
|
|
|
- ["Rahil Momin", "https://github.com/iamrahil"]
|
2014-09-27 23:04:25 +04:00
|
|
|
|
- ["Gregrory Kielian", "https://github.com/gskielian"]
|
2015-04-26 20:22:48 +03:00
|
|
|
|
- ["Etan Reisner", "https://github.com/deryni"]
|
2019-08-10 20:56:02 +03:00
|
|
|
|
- ["Jonathan Wang", "https://github.com/Jonathansw"]
|
2016-07-10 10:04:08 +03:00
|
|
|
|
- ["Leo Rudberg", "https://github.com/LOZORD"]
|
|
|
|
|
- ["Betsy Lorton", "https://github.com/schbetsy"]
|
|
|
|
|
- ["John Detter", "https://github.com/jdetter"]
|
2017-10-02 16:10:53 +03:00
|
|
|
|
- ["Harry Mumford-Turner", "https://github.com/harrymt"]
|
2018-01-16 18:27:30 +03:00
|
|
|
|
- ["Martin Nicholson", "https://github.com/mn113"]
|
2021-08-22 21:15:03 +03:00
|
|
|
|
- ["Mark Grimwood", "https://github.com/MarkGrimwood"]
|
2022-08-19 02:47:37 +03:00
|
|
|
|
- ["Emily Grace Seville", "https://github.com/EmilySeville7cfg"]
|
2013-08-18 02:59:35 +04:00
|
|
|
|
filename: LearnBash.sh
|
2019-08-10 20:56:02 +03:00
|
|
|
|
translators:
|
|
|
|
|
- ["Dimitri Kokkonis", "https://github.com/kokkonisd"]
|
2013-08-18 02:59:35 +04:00
|
|
|
|
---
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
Bash is a name of the unix shell, which was also distributed as the shell
|
2020-08-01 18:54:19 +03:00
|
|
|
|
for the GNU operating system and as the default shell on most Linux distros.
|
2018-12-24 01:59:11 +03:00
|
|
|
|
Nearly all examples below can be a part of a shell script
|
|
|
|
|
or executed directly in the shell.
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
2021-01-29 14:56:11 +03:00
|
|
|
|
[Read more here.](https://www.gnu.org/software/bash/manual/bashref.html)
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
|
|
```bash
|
2018-07-26 00:58:31 +03:00
|
|
|
|
#!/usr/bin/env bash
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# First line of the script is the shebang which tells the system how to execute
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# the script: https://en.wikipedia.org/wiki/Shebang_(Unix)
|
2013-08-18 02:59:35 +04:00
|
|
|
|
# As you already figured, comments start with #. Shebang is also a comment.
|
|
|
|
|
|
|
|
|
|
# Simple hello world example:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
echo "Hello world!" # => Hello world!
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Each command starts on a new line, or after a semicolon:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
echo "This is the first command"; echo "This is the second command"
|
2022-08-19 02:53:55 +03:00
|
|
|
|
# => This is the first command
|
|
|
|
|
# => This is the second command
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
|
|
# Declaring a variable looks like this:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
variable="Some string"
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
|
|
# But not like this:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
variable = "Some string" # => returns error "variable: command not found"
|
|
|
|
|
# Bash will decide that `variable` is a command it must execute and give an error
|
2015-04-26 20:32:41 +03:00
|
|
|
|
# because it can't be found.
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Nor like this:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
variable= "Some string" # => returns error: "Some string: command not found"
|
|
|
|
|
# Bash will decide that "Some string" is a command it must execute and give an
|
|
|
|
|
# error because it can't be found. In this case the "variable=" part is seen
|
|
|
|
|
# as a variable assignment valid only for the scope of the "Some string"
|
|
|
|
|
# command.
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
|
|
|
|
# Using the variable:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
echo "$variable" # => Some string
|
|
|
|
|
echo '$variable' # => $variable
|
2022-08-19 03:20:15 +03:00
|
|
|
|
# When you use a variable itself — assign it, export it, or else — you write
|
2015-10-02 17:08:27 +03:00
|
|
|
|
# its name without $. If you want to use the variable's value, you should use $.
|
2013-09-22 08:29:05 +04:00
|
|
|
|
# Note that ' (single quote) won't expand the variables!
|
2022-08-19 02:47:37 +03:00
|
|
|
|
# You can write variable without surrounding quotes but it's not recommended.
|
|
|
|
|
|
|
|
|
|
# Parameter expansion ${...}:
|
|
|
|
|
echo "${variable}" # => Some string
|
|
|
|
|
# This is a simple usage of parameter expansion such as two examples above.
|
|
|
|
|
# Parameter expansion gets a value from a variable.
|
|
|
|
|
# It "expands" or prints the value.
|
|
|
|
|
# During the expansion time the value or parameter can be modified.
|
|
|
|
|
# Below are other modifications that add onto this expansion.
|
|
|
|
|
|
|
|
|
|
# String substitution in variables:
|
|
|
|
|
echo "${variable/Some/A}" # => A string
|
|
|
|
|
# This will substitute the first occurrence of "Some" with "A".
|
|
|
|
|
|
|
|
|
|
# Substring from a variable:
|
|
|
|
|
length=7
|
|
|
|
|
echo "${variable:0:length}" # => Some st
|
2014-02-28 20:24:45 +04:00
|
|
|
|
# This will return only the first 7 characters of the value
|
2022-08-19 02:47:37 +03:00
|
|
|
|
echo "${variable: -5}" # => tring
|
|
|
|
|
# This will return the last 5 characters (note the space before -5).
|
|
|
|
|
# The space before minus is mandatory here.
|
2018-01-16 18:31:32 +03:00
|
|
|
|
|
2022-08-19 02:47:37 +03:00
|
|
|
|
# String length:
|
|
|
|
|
echo "${#variable}" # => 11
|
2014-02-28 20:24:45 +04:00
|
|
|
|
|
2022-08-19 02:47:37 +03:00
|
|
|
|
# Indirect expansion:
|
|
|
|
|
other_variable="variable"
|
|
|
|
|
echo ${!other_variable} # => Some string
|
|
|
|
|
# This will expand the value of `other_variable`.
|
2020-04-20 21:35:47 +03:00
|
|
|
|
|
2022-08-19 03:20:15 +03:00
|
|
|
|
# The default value for variable:
|
2022-08-19 02:47:37 +03:00
|
|
|
|
echo "${foo:-"DefaultValueIfFooIsMissingOrEmpty"}"
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => DefaultValueIfFooIsMissingOrEmpty
|
2022-08-19 02:47:37 +03:00
|
|
|
|
# This works for null (foo=) and empty string (foo=""); zero (foo=0) returns 0.
|
2015-05-02 15:21:03 +03:00
|
|
|
|
# Note that it only returns default value and doesn't change variable value.
|
2013-12-18 12:37:27 +04:00
|
|
|
|
|
2022-08-19 03:10:34 +03:00
|
|
|
|
# Declare an array with 6 elements:
|
|
|
|
|
array=(one two three four five six)
|
|
|
|
|
# Print the first element:
|
|
|
|
|
echo "${array[0]}" # => "one"
|
|
|
|
|
# Print all elements:
|
|
|
|
|
echo "${array[@]}" # => "one two three four five six"
|
|
|
|
|
# Print the number of elements:
|
|
|
|
|
echo "${#array[@]}" # => "6"
|
|
|
|
|
# Print the number of characters in third element
|
|
|
|
|
echo "${#array[2]}" # => "5"
|
|
|
|
|
# Print 2 elements starting from fourth:
|
|
|
|
|
echo "${array[@]:3:2}" # => "four five"
|
|
|
|
|
# Print all elements each of them on new line.
|
|
|
|
|
for item in "${array[@]}"; do
|
|
|
|
|
echo "$item"
|
2017-11-14 22:30:57 +03:00
|
|
|
|
done
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Built-in variables:
|
2022-08-19 03:10:34 +03:00
|
|
|
|
# There are some useful built-in variables, like:
|
2015-10-02 17:08:27 +03:00
|
|
|
|
echo "Last program's return value: $?"
|
2013-09-22 08:29:05 +04:00
|
|
|
|
echo "Script's PID: $$"
|
2015-10-02 17:08:27 +03:00
|
|
|
|
echo "Number of arguments passed to script: $#"
|
|
|
|
|
echo "All arguments passed to script: $@"
|
|
|
|
|
echo "Script's arguments separated into different variables: $1 $2..."
|
2013-08-18 03:14:00 +04:00
|
|
|
|
|
2022-08-19 03:10:34 +03:00
|
|
|
|
# Brace Expansion {...}
|
|
|
|
|
# used to generate arbitrary strings:
|
|
|
|
|
echo {1..10} # => 1 2 3 4 5 6 7 8 9 10
|
|
|
|
|
echo {a..z} # => a b c d e f g h i j k l m n o p q r s t u v w x y z
|
|
|
|
|
# This will output the range from the start value to the end value.
|
|
|
|
|
# Note that you can't use variables here:
|
|
|
|
|
from=1
|
|
|
|
|
to=10
|
|
|
|
|
echo {$from..$to} # => {$from..$to}
|
|
|
|
|
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# Now that we know how to echo and use variables,
|
2022-08-19 04:09:16 +03:00
|
|
|
|
# let's learn some of the other basics of Bash!
|
2016-07-10 10:04:08 +03:00
|
|
|
|
|
2016-10-02 20:16:12 +03:00
|
|
|
|
# Our current directory is available through the command `pwd`.
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# `pwd` stands for "print working directory".
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# We can also use the built-in variable `$PWD`.
|
2016-10-02 20:16:12 +03:00
|
|
|
|
# Observe that the following are equivalent:
|
2016-07-10 10:04:08 +03:00
|
|
|
|
echo "I'm in $(pwd)" # execs `pwd` and interpolates output
|
|
|
|
|
echo "I'm in $PWD" # interpolates the variable
|
|
|
|
|
|
|
|
|
|
# If you get too much output in your terminal, or from a script, the command
|
2022-08-19 04:09:16 +03:00
|
|
|
|
# `clear` clears your screen:
|
2016-07-10 10:04:08 +03:00
|
|
|
|
clear
|
2022-08-19 04:09:16 +03:00
|
|
|
|
# Ctrl-L also works for clearing output.
|
2016-07-10 10:04:08 +03:00
|
|
|
|
|
2013-08-18 03:14:00 +04:00
|
|
|
|
# Reading a value from input:
|
|
|
|
|
echo "What's your name?"
|
2022-08-19 04:09:16 +03:00
|
|
|
|
read name
|
|
|
|
|
# Note that we didn't need to declare a new variable.
|
|
|
|
|
echo "Hello, $name!"
|
2013-08-18 02:59:35 +04:00
|
|
|
|
|
2022-08-19 04:09:16 +03:00
|
|
|
|
# We have the usual if structure.
|
|
|
|
|
# Condition is true if the value of $name is not equal to the current user's login username:
|
|
|
|
|
if [[ "$name" != "$USER" ]]; then
|
2013-12-27 19:21:24 +04:00
|
|
|
|
echo "Your name isn't your username"
|
2014-08-23 10:54:13 +04:00
|
|
|
|
else
|
|
|
|
|
echo "Your name is your username"
|
2013-08-18 02:59:35 +04:00
|
|
|
|
fi
|
|
|
|
|
|
2022-08-19 04:09:16 +03:00
|
|
|
|
# To use && and || with if statements, you need multiple pairs of square brackets:
|
|
|
|
|
read age
|
|
|
|
|
if [[ "$name" == "Steve" ]] && [[ "$age" -eq 15 ]]; then
|
|
|
|
|
echo "This will run if $name is Steve AND $age is 15."
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
if [[ "$name" == "Daniya" ]] || [[ "$name" == "Zach" ]]; then
|
|
|
|
|
echo "This will run if $name is Daniya OR Zach."
|
|
|
|
|
fi
|
|
|
|
|
# There are other comparison operators for numbers listed below:
|
|
|
|
|
# -ne - not equal
|
|
|
|
|
# -lt - less than
|
|
|
|
|
# -gt - greater than
|
|
|
|
|
# -le - less than or equal to
|
|
|
|
|
# -ge - greater than or equal to
|
|
|
|
|
|
|
|
|
|
# There is also the `=~` operator, which tests a string against the Regex pattern:
|
|
|
|
|
email=me@example.com
|
|
|
|
|
if [[ "$email" =~ [a-z]+@[a-z]{2,}\.(com|net|org) ]]
|
|
|
|
|
then
|
|
|
|
|
echo "Valid email!"
|
|
|
|
|
fi
|
2015-10-14 18:40:28 +03:00
|
|
|
|
|
2013-09-22 08:06:35 +04:00
|
|
|
|
# There is also conditional execution
|
2013-12-27 19:21:24 +04:00
|
|
|
|
echo "Always executed" || echo "Only executed if first command fails"
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => Always executed
|
2013-09-22 08:06:35 +04:00
|
|
|
|
echo "Always executed" && echo "Only executed if first command does NOT fail"
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => Always executed
|
|
|
|
|
# => Only executed if first command does NOT fail
|
|
|
|
|
|
2022-01-03 20:00:53 +03:00
|
|
|
|
# A single ampersand & after a command runs it in the background. A background command's
|
|
|
|
|
# output is printed to the terminal, but it cannot read from the input.
|
|
|
|
|
sleep 30 &
|
|
|
|
|
# List background jobs
|
|
|
|
|
jobs # => [1]+ Running sleep 30 &
|
|
|
|
|
# Bring the background job to the foreground
|
|
|
|
|
fg
|
|
|
|
|
# Ctrl-C to kill the process, or Ctrl-Z to pause it
|
|
|
|
|
# Resume a background process after it has been paused with Ctrl-Z
|
|
|
|
|
bg
|
|
|
|
|
# Kill job number 2
|
|
|
|
|
kill %2
|
|
|
|
|
# %1, %2, etc. can be used for fg and bg as well
|
2013-08-23 00:26:26 +04:00
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Redefine command `ping` as alias to send only 5 packets
|
2017-11-14 22:30:57 +03:00
|
|
|
|
alias ping='ping -c 5'
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Escape the alias and use command with this name instead
|
2017-11-14 22:30:57 +03:00
|
|
|
|
\ping 192.168.1.1
|
|
|
|
|
# Print all aliases
|
|
|
|
|
alias -p
|
2014-08-06 22:30:15 +04:00
|
|
|
|
|
2013-08-18 03:14:00 +04:00
|
|
|
|
# Expressions are denoted with the following format:
|
2017-09-29 19:09:39 +03:00
|
|
|
|
echo $(( 10 + 5 )) # => 15
|
2013-08-18 03:14:00 +04:00
|
|
|
|
|
2015-10-02 17:08:27 +03:00
|
|
|
|
# Unlike other programming languages, bash is a shell so it works in the context
|
|
|
|
|
# of a current directory. You can list files and directories in the current
|
2013-12-27 19:21:24 +04:00
|
|
|
|
# directory with the ls command:
|
2017-09-29 19:09:39 +03:00
|
|
|
|
ls # Lists the files and subdirectories contained in the current directory
|
2013-08-18 16:25:20 +04:00
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# This command has options that control its execution:
|
2013-08-18 16:25:20 +04:00
|
|
|
|
ls -l # Lists every file and directory on a separate line
|
2017-02-12 18:06:21 +03:00
|
|
|
|
ls -t # Sorts the directory contents by last-modified date (descending)
|
2016-07-10 10:04:08 +03:00
|
|
|
|
ls -R # Recursively `ls` this directory and all of its subdirectories
|
2013-08-18 16:25:20 +04:00
|
|
|
|
|
2022-01-03 20:02:22 +03:00
|
|
|
|
# Results (stdout) of the previous command can be passed as input (stdin) to the next command
|
|
|
|
|
# using a pipe |. Commands chained in this way are called a "pipeline", and are run concurrently.
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# The `grep` command filters the input with provided patterns.
|
|
|
|
|
# That's how we can list .txt files in the current directory:
|
2013-08-18 16:25:20 +04:00
|
|
|
|
ls -l | grep "\.txt"
|
|
|
|
|
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# Use `cat` to print files to stdout:
|
|
|
|
|
cat file.txt
|
|
|
|
|
|
|
|
|
|
# We can also read the file using `cat`:
|
|
|
|
|
Contents=$(cat file.txt)
|
2020-04-17 03:37:30 +03:00
|
|
|
|
# "\n" prints a new line character
|
2020-08-01 18:54:19 +03:00
|
|
|
|
# "-e" to interpret the newline escape characters as escape characters
|
2020-04-17 03:37:30 +03:00
|
|
|
|
echo -e "START OF FILE\n$Contents\nEND OF FILE"
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => START OF FILE
|
|
|
|
|
# => [contents of file.txt]
|
|
|
|
|
# => END OF FILE
|
2016-07-10 10:04:08 +03:00
|
|
|
|
|
|
|
|
|
# Use `cp` to copy files or directories from one place to another.
|
|
|
|
|
# `cp` creates NEW versions of the sources,
|
|
|
|
|
# so editing the copy won't affect the original (and vice versa).
|
|
|
|
|
# Note that it will overwrite the destination if it already exists.
|
|
|
|
|
cp srcFile.txt clone.txt
|
|
|
|
|
cp -r srcDirectory/ dst/ # recursively copy
|
|
|
|
|
|
|
|
|
|
# Look into `scp` or `sftp` if you plan on exchanging files between computers.
|
|
|
|
|
# `scp` behaves very similarly to `cp`.
|
|
|
|
|
# `sftp` is more interactive.
|
|
|
|
|
|
|
|
|
|
# Use `mv` to move files or directories from one place to another.
|
|
|
|
|
# `mv` is similar to `cp`, but it deletes the source.
|
|
|
|
|
# `mv` is also useful for renaming files!
|
|
|
|
|
mv s0urc3.txt dst.txt # sorry, l33t hackers...
|
|
|
|
|
|
2019-08-10 20:56:02 +03:00
|
|
|
|
# Since bash works in the context of a current directory, you might want to
|
2015-10-19 00:20:55 +03:00
|
|
|
|
# run your command in some other directory. We have cd for changing location:
|
|
|
|
|
cd ~ # change to home directory
|
2018-10-03 05:23:45 +03:00
|
|
|
|
cd # also goes to home directory
|
2015-10-19 00:20:55 +03:00
|
|
|
|
cd .. # go up one directory
|
|
|
|
|
# (^^say, from /home/username/Downloads to /home/username)
|
|
|
|
|
cd /home/username/Documents # change to specified directory
|
2022-01-03 20:02:22 +03:00
|
|
|
|
cd ~/Documents/.. # now in home directory (if ~/Documents exists)
|
2018-10-03 05:23:45 +03:00
|
|
|
|
cd - # change to last directory
|
|
|
|
|
# => /home/username/Documents
|
2015-10-19 00:20:55 +03:00
|
|
|
|
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# Use subshells to work across directories
|
|
|
|
|
(echo "First, I'm here: $PWD") && (cd someDir; echo "Then, I'm here: $PWD")
|
|
|
|
|
pwd # still in first directory
|
|
|
|
|
|
|
|
|
|
# Use `mkdir` to create new directories.
|
|
|
|
|
mkdir myNewDir
|
|
|
|
|
# The `-p` flag causes new intermediate directories to be created as necessary.
|
|
|
|
|
mkdir -p myNewDir/with/intermediate/directories
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# if the intermediate directories didn't already exist, running the above
|
|
|
|
|
# command without the `-p` flag would return an error
|
2015-10-19 00:20:55 +03:00
|
|
|
|
|
2022-01-03 20:02:22 +03:00
|
|
|
|
# You can redirect command input and output (stdin, stdout, and stderr)
|
|
|
|
|
# using "redirection operators". Unlike a pipe, which passes output to a command,
|
|
|
|
|
# a redirection operator has a command's input come from a file or stream, or
|
|
|
|
|
# sends its output to a file or stream.
|
|
|
|
|
|
2014-10-31 03:20:05 +03:00
|
|
|
|
# Read from stdin until ^EOF$ and overwrite hello.py with the lines
|
2022-01-03 20:02:22 +03:00
|
|
|
|
# between "EOF" (which are called a "here document"):
|
2014-10-31 03:20:05 +03:00
|
|
|
|
cat > hello.py << EOF
|
|
|
|
|
#!/usr/bin/env python
|
|
|
|
|
from __future__ import print_function
|
|
|
|
|
import sys
|
|
|
|
|
print("#stdout", file=sys.stdout)
|
|
|
|
|
print("#stderr", file=sys.stderr)
|
|
|
|
|
for line in sys.stdin:
|
|
|
|
|
print(line, file=sys.stdout)
|
|
|
|
|
EOF
|
2018-10-03 05:19:18 +03:00
|
|
|
|
# Variables will be expanded if the first "EOF" is not quoted
|
2014-10-31 03:20:05 +03:00
|
|
|
|
|
2019-08-10 20:56:02 +03:00
|
|
|
|
# Run the hello.py Python script with various stdin, stdout, and
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# stderr redirections:
|
|
|
|
|
python hello.py < "input.in" # pass input.in as input to the script
|
2018-12-24 01:59:11 +03:00
|
|
|
|
|
2017-09-29 19:09:39 +03:00
|
|
|
|
python hello.py > "output.out" # redirect output from the script to output.out
|
2018-12-24 01:59:11 +03:00
|
|
|
|
|
2017-09-29 19:09:39 +03:00
|
|
|
|
python hello.py 2> "error.err" # redirect error output to error.err
|
2018-12-24 01:59:11 +03:00
|
|
|
|
|
|
|
|
|
python hello.py > "output-and-error.log" 2>&1
|
|
|
|
|
# redirect both output and errors to output-and-error.log
|
2022-01-03 20:02:22 +03:00
|
|
|
|
# &1 means file descriptor 1 (stdout), so 2>&1 redirects stderr (2) to the current
|
|
|
|
|
# destination of stdout (1), which has been redirected to output-and-error.log.
|
2018-12-24 01:59:11 +03:00
|
|
|
|
|
|
|
|
|
python hello.py > /dev/null 2>&1
|
|
|
|
|
# redirect all output and errors to the black hole, /dev/null, i.e., no output
|
|
|
|
|
|
2014-10-31 03:20:05 +03:00
|
|
|
|
# The output error will overwrite the file if it exists,
|
|
|
|
|
# if you want to append instead, use ">>":
|
|
|
|
|
python hello.py >> "output.out" 2>> "error.err"
|
|
|
|
|
|
2015-05-12 05:20:02 +03:00
|
|
|
|
# Overwrite output.out, append to error.err, and count lines:
|
2014-10-31 03:20:05 +03:00
|
|
|
|
info bash 'Basic Shell Features' 'Redirections' > output.out 2>> error.err
|
|
|
|
|
wc -l output.out error.err
|
|
|
|
|
|
|
|
|
|
# Run a command and print its file descriptor (e.g. /dev/fd/123)
|
|
|
|
|
# see: man fd
|
|
|
|
|
echo <(echo "#helloworld")
|
|
|
|
|
|
2015-05-12 05:20:02 +03:00
|
|
|
|
# Overwrite output.out with "#helloworld":
|
2014-10-31 03:20:05 +03:00
|
|
|
|
cat > output.out <(echo "#helloworld")
|
|
|
|
|
echo "#helloworld" > output.out
|
|
|
|
|
echo "#helloworld" | cat > output.out
|
|
|
|
|
echo "#helloworld" | tee output.out >/dev/null
|
|
|
|
|
|
|
|
|
|
# Cleanup temporary files verbosely (add '-i' for interactive)
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# WARNING: `rm` commands cannot be undone
|
2014-10-31 03:20:05 +03:00
|
|
|
|
rm -v output.out error.err output-and-error.log
|
2016-07-10 10:04:08 +03:00
|
|
|
|
rm -r tempDir/ # recursively delete
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# You can install the `trash-cli` Python package to have `trash`
|
|
|
|
|
# which puts files in the system trash and doesn't delete them directly
|
|
|
|
|
# see https://pypi.org/project/trash-cli/ if you want to be careful
|
2013-09-22 18:04:24 +04:00
|
|
|
|
|
2013-10-04 19:32:11 +04:00
|
|
|
|
# Commands can be substituted within other commands using $( ):
|
2013-08-19 20:14:02 +04:00
|
|
|
|
# The following command displays the number of files and directories in the
|
|
|
|
|
# current directory.
|
2013-08-18 04:33:32 +04:00
|
|
|
|
echo "There are $(ls | wc -l) items here."
|
|
|
|
|
|
2019-08-10 20:56:02 +03:00
|
|
|
|
# The same can be done using backticks `` but they can't be nested -
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# the preferred way is to use $( ).
|
2013-12-09 16:17:20 +04:00
|
|
|
|
echo "There are `ls | wc -l` items here."
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Bash uses a `case` statement that works similarly to switch in Java and C++:
|
2015-04-30 05:11:20 +03:00
|
|
|
|
case "$Variable" in
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# List patterns for the conditions you want to meet
|
2013-08-31 15:35:04 +04:00
|
|
|
|
0) echo "There is a zero.";;
|
|
|
|
|
1) echo "There is a one.";;
|
2021-01-29 14:56:11 +03:00
|
|
|
|
*) echo "It is not null.";; # match everything
|
2013-08-18 04:33:32 +04:00
|
|
|
|
esac
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# `for` loops iterate for as many arguments given:
|
2015-04-30 05:11:20 +03:00
|
|
|
|
# The contents of $Variable is printed three times.
|
|
|
|
|
for Variable in {1..3}
|
2013-08-18 04:33:32 +04:00
|
|
|
|
do
|
2015-04-30 05:11:20 +03:00
|
|
|
|
echo "$Variable"
|
2013-08-18 04:33:32 +04:00
|
|
|
|
done
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => 1
|
|
|
|
|
# => 2
|
|
|
|
|
# => 3
|
|
|
|
|
|
2013-08-18 04:33:32 +04:00
|
|
|
|
|
2014-09-06 05:51:48 +04:00
|
|
|
|
# Or write it the "traditional for loop" way:
|
|
|
|
|
for ((a=1; a <= 3; a++))
|
|
|
|
|
do
|
|
|
|
|
echo $a
|
|
|
|
|
done
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => 1
|
|
|
|
|
# => 2
|
|
|
|
|
# => 3
|
2014-09-06 05:51:48 +04:00
|
|
|
|
|
2014-08-08 21:24:43 +04:00
|
|
|
|
# They can also be used to act on files..
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# This will run the command `cat` on file1 and file2
|
2015-04-30 05:11:20 +03:00
|
|
|
|
for Variable in file1 file2
|
2014-08-08 21:24:43 +04:00
|
|
|
|
do
|
2015-04-30 05:11:20 +03:00
|
|
|
|
cat "$Variable"
|
2014-08-08 21:24:43 +04:00
|
|
|
|
done
|
|
|
|
|
|
|
|
|
|
# ..or the output from a command
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# This will `cat` the output from `ls`.
|
2015-04-30 05:11:20 +03:00
|
|
|
|
for Output in $(ls)
|
2014-08-08 21:24:43 +04:00
|
|
|
|
do
|
2015-04-30 05:11:20 +03:00
|
|
|
|
cat "$Output"
|
2014-08-08 21:24:43 +04:00
|
|
|
|
done
|
|
|
|
|
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# Bash can also accept patterns, like this to `cat`
|
|
|
|
|
# all the Markdown files in current directory
|
|
|
|
|
for Output in ./*.markdown
|
|
|
|
|
do
|
|
|
|
|
cat "$Output"
|
|
|
|
|
done
|
|
|
|
|
|
2013-11-25 19:42:37 +04:00
|
|
|
|
# while loop:
|
2014-08-08 21:11:17 +04:00
|
|
|
|
while [ true ]
|
2013-11-25 19:42:37 +04:00
|
|
|
|
do
|
|
|
|
|
echo "loop body here..."
|
|
|
|
|
break
|
|
|
|
|
done
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# => loop body here...
|
2013-11-25 19:42:37 +04:00
|
|
|
|
|
2013-09-22 18:28:59 +04:00
|
|
|
|
# You can also define functions
|
|
|
|
|
# Definition:
|
2013-10-13 07:14:24 +04:00
|
|
|
|
function foo ()
|
2013-09-22 18:28:59 +04:00
|
|
|
|
{
|
|
|
|
|
echo "Arguments work just like script arguments: $@"
|
|
|
|
|
echo "And: $1 $2..."
|
|
|
|
|
echo "This is a function"
|
2021-08-22 21:15:03 +03:00
|
|
|
|
returnValue=0 # Variable values can be returned
|
|
|
|
|
return $returnValue
|
2013-09-22 18:28:59 +04:00
|
|
|
|
}
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# Call the function `foo` with two arguments, arg1 and arg2:
|
|
|
|
|
foo arg1 arg2
|
|
|
|
|
# => Arguments work just like script arguments: arg1 arg2
|
|
|
|
|
# => And: arg1 arg2...
|
|
|
|
|
# => This is a function
|
2021-08-22 21:15:03 +03:00
|
|
|
|
# Return values can be obtained with $?
|
|
|
|
|
resultValue=$?
|
|
|
|
|
# More than 9 arguments are also possible by using braces, e.g. ${10}, ${11}, ...
|
2013-09-22 18:28:59 +04:00
|
|
|
|
|
2013-10-13 07:14:24 +04:00
|
|
|
|
# or simply
|
|
|
|
|
bar ()
|
|
|
|
|
{
|
|
|
|
|
echo "Another way to declare functions!"
|
|
|
|
|
return 0
|
|
|
|
|
}
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# Call the function `bar` with no arguments:
|
|
|
|
|
bar # => Another way to declare functions!
|
2013-10-13 07:14:24 +04:00
|
|
|
|
|
2013-09-22 18:28:59 +04:00
|
|
|
|
# Calling your function
|
2015-04-30 05:11:20 +03:00
|
|
|
|
foo "My name is" $Name
|
2013-09-22 18:35:04 +04:00
|
|
|
|
|
|
|
|
|
# There are a lot of useful commands you should learn:
|
|
|
|
|
# prints last 10 lines of file.txt
|
2014-07-23 10:32:50 +04:00
|
|
|
|
tail -n 10 file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2013-09-22 18:35:04 +04:00
|
|
|
|
# prints first 10 lines of file.txt
|
2014-07-23 10:32:50 +04:00
|
|
|
|
head -n 10 file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2022-01-03 20:00:05 +03:00
|
|
|
|
# print file.txt's lines in sorted order
|
2014-07-23 10:32:50 +04:00
|
|
|
|
sort file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2013-09-22 18:35:04 +04:00
|
|
|
|
# report or omit repeated lines, with -d it reports them
|
2014-07-23 10:32:50 +04:00
|
|
|
|
uniq -d file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2013-09-22 18:35:04 +04:00
|
|
|
|
# prints only the first column before the ',' character
|
2014-07-23 10:32:50 +04:00
|
|
|
|
cut -d ',' -f 1 file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
|
|
|
|
# replaces every occurrence of 'okay' with 'great' in file.txt
|
|
|
|
|
# (regex compatible)
|
2014-10-05 01:50:00 +04:00
|
|
|
|
sed -i 's/okay/great/g' file.txt
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# be aware that this -i flag means that file.txt will be changed
|
|
|
|
|
# -i or --in-place erase the input file (use --in-place=.backup to keep a back-up)
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2015-04-24 00:06:54 +03:00
|
|
|
|
# print to stdout all lines of file.txt which match some regex
|
|
|
|
|
# The example prints lines which begin with "foo" and end in "bar"
|
2014-10-05 01:50:00 +04:00
|
|
|
|
grep "^foo.*bar$" file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2014-10-05 01:50:00 +04:00
|
|
|
|
# pass the option "-c" to instead print the number of lines matching the regex
|
|
|
|
|
grep -c "^foo.*bar$" file.txt
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# Other useful options are:
|
|
|
|
|
grep -r "^foo.*bar$" someDir/ # recursively `grep`
|
|
|
|
|
grep -n "^foo.*bar$" file.txt # give line numbers
|
|
|
|
|
grep -rI "^foo.*bar$" someDir/ # recursively `grep`, but ignore binary files
|
2017-09-29 19:09:39 +03:00
|
|
|
|
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# perform the same initial search, but filter out the lines containing "baz"
|
|
|
|
|
grep "^foo.*bar$" file.txt | grep -v "baz"
|
|
|
|
|
|
2015-04-24 00:06:54 +03:00
|
|
|
|
# if you literally want to search for the string,
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# and not the regex, use `fgrep` (or `grep -F`)
|
2016-05-12 14:07:50 +03:00
|
|
|
|
fgrep "foobar" file.txt
|
2014-10-31 03:46:37 +03:00
|
|
|
|
|
2019-08-10 20:56:02 +03:00
|
|
|
|
# The `trap` command allows you to execute a command whenever your script
|
|
|
|
|
# receives a signal. Here, `trap` will execute `rm` if it receives any of the
|
2017-09-29 19:09:39 +03:00
|
|
|
|
# three listed signals.
|
2016-06-26 15:38:05 +03:00
|
|
|
|
trap "rm $TEMP_FILE; exit" SIGHUP SIGINT SIGTERM
|
2014-10-31 03:46:37 +03:00
|
|
|
|
|
2016-07-10 10:04:08 +03:00
|
|
|
|
# `sudo` is used to perform commands as the superuser
|
2021-01-29 14:56:11 +03:00
|
|
|
|
# usually it will ask interactively the password of superuser
|
2016-10-13 09:25:44 +03:00
|
|
|
|
NAME1=$(whoami)
|
|
|
|
|
NAME2=$(sudo whoami)
|
2016-07-10 10:04:08 +03:00
|
|
|
|
echo "Was $NAME1, then became more powerful $NAME2"
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Read Bash shell built-ins documentation with the bash `help` built-in:
|
2014-10-31 03:46:37 +03:00
|
|
|
|
help
|
|
|
|
|
help help
|
|
|
|
|
help for
|
|
|
|
|
help return
|
|
|
|
|
help source
|
|
|
|
|
help .
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Read Bash manpage documentation with `man`
|
2014-10-31 03:46:37 +03:00
|
|
|
|
apropos bash
|
|
|
|
|
man 1 bash
|
|
|
|
|
man bash
|
|
|
|
|
|
2018-12-24 01:59:11 +03:00
|
|
|
|
# Read info documentation with `info` (`?` for help)
|
2014-10-31 03:46:37 +03:00
|
|
|
|
apropos info | grep '^info.*('
|
|
|
|
|
man info
|
|
|
|
|
info info
|
|
|
|
|
info 5 info
|
|
|
|
|
|
|
|
|
|
# Read bash info documentation:
|
|
|
|
|
info bash
|
|
|
|
|
info bash 'Bash Features'
|
|
|
|
|
info bash 6
|
|
|
|
|
info --apropos bash
|
2013-08-18 04:33:32 +04:00
|
|
|
|
```
|