06-14-2010
Quote:
Originally Posted by
thedoobieman5
OK now something else is happening I don't get. When I run the command it only works for directories, otherwise I get an error message. I thought the "$@" was supposed to include all possible arguments?
"$@" represents all the arguments.
If you called the script with * as the argument, the shell will expand it and the script will see all the files (including subdirectories) in the current directory (not including dot files), each stored as a separate argument in "$@".
This User Gave Thanks to cfajohnson For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to figure out how to build a small shell script that will find old .shtml files in every /tgp/ directory on the server and delete them if they are older than 10 days...
The structure of the paths are like this:
/home/domains/www.domain2.com/tgp/
/home/domains/www.domain3.com/tgp/... (1 Reply)
Discussion started by: Neko
1 Replies
2. UNIX for Dummies Questions & Answers
what will the cmd below do?
ls *.3
1 members mentions that to seek all permutations and combinations of the mp3 extension ill have to use curly braces, {} and not, .
what then will do? (13 Replies)
Discussion started by: abhi
13 Replies
3. Shell Programming and Scripting
Hi, I have this code to search all "cif" files using wildcard
for file in *.cif
do
grep "Uiso" $file | awk '{ print $3, $4, $5 }' > tet
done
I get this error
"grep: *.cif: No such file or directory"
Please where am I going wrong!!!
Thank you in advance (6 Replies)
Discussion started by: princessotes
6 Replies
4. Shell Programming and Scripting
This might be a simple answer but I can't for my life figure it out. If I input "bat", how do I get the condition to pick it up with the wild card *at*.
#!/bin/bash
read -p "enter" BOO
if ; then
echo "you win"
else
echo "you lose"
fi (3 Replies)
Discussion started by: zerofire123
3 Replies
5. UNIX for Advanced & Expert Users
Can someone please explain the wildcards in this. How is this recursive? When I put this in my terminal it recursively displayed everything.
ls .* * (6 Replies)
Discussion started by: cokedude
6 Replies
6. Shell Programming and Scripting
Hi,
Can anyone help me how to use * in if statement.
File contains below
line1:a|b|c|Apple-RED|
line2:c|d|e|Apple-Green|
line3:f|g|h|Orange|
I need to find line by line 4th field contains 'Apple' or not.
Please help me at the earliest. (6 Replies)
Discussion started by: jam_prasanna
6 Replies
7. Shell Programming and Scripting
i have got heaps of files (.pdf, .txt and .doc) files in one folder, i am making a program in PERL that helps me find the files i want easier using shell wildcard,
something like this!!
print "Enter a pattern: (must be in )";
$input = <STDIN>;
if (The input is in and valid wildcard... (3 Replies)
Discussion started by: bshell_1214
3 Replies
8. Shell Programming and Scripting
Hi Experts,
I want to use ls in the below form:
ls -l *.{txt,TXT} (working fine)
but when i am declaring a variable,
VAR="*.{txt,TXT}"
ls -l $VAR is not working. Please help.
Thanks. (4 Replies)
Discussion started by: sugarcane
4 Replies
9. Shell Programming and Scripting
Hi Folks,
I had a requirement to replace a pattern a.*a with 'a' alone. I'm writing a sed command to do that. But I'm not able to work this out. Pls help me.
echo 'a123a456a789' | sed 's/a.*a/a/'
Expected o/p : a456a789
But actual o/p is a789. :confused:
how can write that... (6 Replies)
Discussion started by: poova
6 Replies
10. OS X (Apple)
CD_numb is AM017
this code:
set the_Firstcom_CD to (do shell script "ls -d '/volumes/audioNAS/Firstcom/Access Music/' ") & CD_numb
gives me this:
"/volumes/audioNAS/Firstcom/Access Music/AM017"
the item I am looking for is AM017Q.
I can get the "*" syntax right so it never finder... (7 Replies)
Discussion started by: sbrady
7 Replies
LEARN ABOUT DEBIAN
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)
NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS
--debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)