Search Results

array_save()
{
eval "printf '%s\n' \"\${${x}[@]}\""
} > "${2:-/dev/tty}"

Top Ten Reasons not to use the C shell (http://www.grymoire.com/Unix/CshTop10.txt) Csh problems (http://www.grymoire.com/Unix/Csh.html#uh-0) Csh Programming Considered Harmful...

If you have the output in a variable, you don't need any external command:

output='Device "nrst3a" attributes=(0x4) RAW SERIAL_NUMBER=SN[VD073AV1443BVW00083]L2'

IFS=\" read a s1 b <<<...

I'd simplify the whole thing by shuffling the deck and then dealing from it.

There are 3 functions in this snippet:
shuffle, which shuffles a standard deck of cards into a space-separated string...

"$*" and "$@" are not exit codes; they are the command line arguments.

Exit codes are stored in "$?".

When unquoted, $* and $@ are the same; each word in the argument list becomes a separate...

awk 'BEGIN { print "<div align=center>" }
{ gsub(/&/,"&amp;"); gsub(/</,"&lt;") }
/^$/ { print; last = "blank"; next }
last == "blank" || NR == 1 {
last = ""
printf " <p>"
}
/THE DISTRICT COURT...

s/crippled/standard/

That will only work with the GNU date command; -d is not standard.



I doubt that OP is using a system without a POSIX shell, so there's no need for cut:

IFS=/ read month day year whatever...

That will fail if $AllFile contains whitespace.

}' "$AllFile.tmp" > "$AllFile"

That is almost almost always the wrong way ro read the contents of a file. Not only is cat unnecssary but it will break your script if any lines contain whitespace or other pathological characters....

Do not use basename. It is an external command that is an order of magnitude slower than using the shell's parameter expansion.

With bash there is no need for any external command:


#!/bin/bash
file=$1

mapfile -t xx < "$file"
n=${#xx[@]}
printf "%s\n" "${xx[@]:1:n-2}"

The best places I have found are this forum and the Usenet newsgroup comp.unix.shell.

First, you don't need -1 when the output of ls is not going to a terminal.

Second, the command will fail if $1 contains whitespace or other pathological characters.

Third, there is no need for...

for f in *
do
[ -s "$f" ] && continue ## file exists, but is not empty
[ -f "$f" ] && rm "$f"
done

Rather than whereis, use type; It tells you what the shell will actually use:


$ type [
[ is a shell builtin


With the -a option, it gives all the possible commands that could be executed:
...

man bash:"Redirections using file descriptors greater than 9 should be used with care, as they may conflict with file descriptors the shell uses internally."

There is no need to use an external command for integer arithmetic in bash (or any other POSIX shell):

count=$(( count + 1 ))


Or, in bash:


(( ++count ))

set -f
IFS='
'
set -- $( cat list2 )
for i in `cat list1`
do
printf "%s %s\n" "$i" "$1"
shift
done

Put this in a script or a function:


n=200 ## adjust to taste: higher value, lighter background
n1=$(( 256 - $n ))
bg=$( printf "#%x%x%x\n" $(( $RANDOM % $n1 + $n )) \
...

If you want to get a value from the command line, use the positional parameters, $1, etc., not 'read'.


case $1 in
1|memory) echo " you've selected check memory..1 sec pls "
...

grep "^$acc;" "$file"

There's no point in sourcing the script if you are putting it in the background.

A background process is not executed in the current shell.

tab=$'\t'
read num
grep "^$num$tab" | cut -f2-

There should be no space after file, and you don't need both $( ... ) and ` ... `.

date=$(date +%Y%m%d)
file=$(find . -name "$date"_*.xml)
mv "$file" renamedfeed_"$date".xml