Bash basics: Difference between revisions

From Bitpost wiki
No edit summary
No edit summary
Line 37: Line 37:
     fi
     fi
fi</pre>
fi</pre>
=== [https://readwrite.com/2010/11/10/how-to-search-your-source-with/ grep your code] ===


=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===
=== [http://www.panix.com/~elflord/unix/grep.html powerful grep options] ===

Revision as of 13:44, 7 July 2017

Bash certainly has its set of snafus.

store commands in variables

# NOTE don't put spaces around equals sign!
# NOTE don't use ampersands within command strings, they won't work
# use a blank command if needed, that's fine
mycmd1="command param param"
mycmd2="cmd2 param"
if [ -e /myspecialplace ]
mycmd2=""
fi
mycmd3="cmd3 param"
$mycmd1 && $mycmd2 && $mycmd3

capture output

myout=`program1 param`;
  • Note the difference a single quote makes to output...
$ eval echo "abc   def"
abc def
$ eval 'echo "abc   def"'
abc   def

check for an error

mkdir "$d2"
if [ $? -gt 0 ]; then
   echo "mkdir error, try that again..."
   exit 3
fi

read input from user

echo "Create the subdirectory?  [$d2]"
if read answer; then
    if [ ${answer} = "y" ] || [ ${answer} = "yes" ]; then
        {whatever}
    else
        {whatever}
    fi
fi

grep your code

powerful grep options