Search Results

sed 's/\( *\)\([0-9][0-9]*$\)/=\2/' inputfile > outfile

try this,
awk '{$(NF-1)=$(NF-1)"="$NF;$NF=""}1' inputfile

Only partially true :
... Or until you specify another match number ...

# echo 'ABCDEFG'
ABCDEFG
# echo 'ABCDEFG' | sed 's/././'
.BCDEFG
# echo 'ABCDEFG' | sed 's/././1'
.BCDEFG
# echo...

sed's s command only hits the first match unless you add a g flag:

$ echo abc 123 def 456 | sed 's|\([a-z]*\) \([0-9]*\)|\1|'
abc def 456
$ echo abc 123 def 456 | sed 's|\([a-z]*\)...

Quick question here: why not just use cp?

var=$(sed 's/:[^#]*##/ /g;s/^[^#]*##//;s/:[^:]*$//' infile)or
var=$(awk -v RS="#" -F: 'NF>1{print $1}' infile)
table=$(awk '{for(i=1;i<=NF;i++)if(tolower($i)=="from")if($(i+1)!~/[(]/)print $(i+1)}'...

type=|set a variable called "type"
(condition)?<value_if_condition_is_verified>:<value_if_condition_is_not_verified_>|this notation is used to test the value of field $3 :...

Quote the echo to preserve the output:


echo "`sqlplus ...
...`" | ....

Why do you need to echo what is already output?

If you specify . ./file.ksh, it's like running the contents of that file in your current shell. It's a bit smarter than this, but think of it running:
while read line; do "$line"; done <file.ksh...

The "." command is executing the script in the calling shell (a.k.a. sourcing it) instead of launching a subshell. This explains the differences you observed.

A

at : execute commands at a specified time/date.
awk: a scripting language, especially useful for manipulating text and automation.

B
bash : invokes the Bourne Again Shell (standard on...