07-22-2012
Quote:
Originally Posted by
Corona688
That's odd that the {} wouldn't be evaluated when used that way, since * definitely is, but it does look like you need eval.
bash performs brace expansion before parameter expansion, so the braces in $VAR aren't special.
However, this would work in ksh, since it performs brace expansion after paremter expansion (just before pathname expansion).
Regards,
Alister
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
Just a quick question:
if I want to do a comparison with a wildcard in a shell script, do i just use '*'? Heres what I have:
elif ; then
continue
but that doesnt evaluate right. It tries to compare against the literal '/apps*' instead of anything that begins with '/apps' (2 Replies)
Discussion started by: rdudejr
2 Replies
4. 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
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
I'm trying to make a small script to see if you say a specific word, in bash.
Here is my code so far :
if ]; then
echo "You typed Something Device Something"
fi
exit 0
It does not echo what it should, even if i type something along the lines of "random Device stuff"
Please help,... (2 Replies)
Discussion started by: DuskFall
2 Replies
9. Shell Programming and Scripting
GNU grep with Oracle Linux 6.3
I want to grep for strings starting with the pattern ora and and having the words r2j in it. It should return the lines highlighted in red below.
But , I think I am not using wildcard for multiple characters correctly.
$ cat someText.txt
ora_pmon_jcpprdvp1... (3 Replies)
Discussion started by: kraljic
3 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 FREEBSD
kpsewhich
KPSEWHICH(1) General Commands Manual KPSEWHICH(1)
NAME
kpsewhich - standalone path lookup and and expansion for kpathsea
SYNOPSIS
kpsewhich [options] [filenames]
DESCRIPTION
This manual page is not meant to be exhaustive. The complete documentation for this version of TeX can be found in the info file or manual
Kpathsea: A library for path searching.
kpsewhich is used as a standalone front-end of the kpathsea library that can be used to examine variables and find files. When the -format
option is not given, the search path used when looking for a file is inferred from the name given, by looking for a known extension. If no
known extension is found, the search path for TeX source files is used.
OPTIONS
kpsewhich accepts the following options:
-debug num
Set debugging flags.
-D num Use a base resolution of num; the default, set by the installer, is typically 600.
-dpi num
As -D.
-engine string
Set $engine in the environment, which is used in some search paths.
-expand-braces string
Print variable and brace expansion of string.
-expand-path string
Print complete path expansion of string.
-expand-var string
Print variable expansion of string.
-format name
Use file type name. See the info manual for a list of valid names, or use the -help option to print the list.
-help Print help message and exit.
-interactive
Ask for additional filenames to look up.
-mktex fmt
enable mktexfmt generation. (fmt=pk/mf/tex/tfm)
-mode string
Set device name for $MAKETEX_MODE to string; no default.
-must-exist
Search the disk as well as ls-R if necessary.
-no-mktex fmt
disable mktexfmt generation. (fmt=pk/mf/tex/tfm)
-path string
Search in the path string.
-progname string
Set program name to string.
-show-path name
Output search path for file type name. See the info manual for a list of valid names, or use the -help option to print the list.
-var-value variable
Print the expansion of variable.
-version
Print version information and exit.
SEE ALSO
mktexlsr(1), mktexmf(1), mktexpk(1), mktextfm(1).
Kpathsea 6.1.0 1 March 2011 KPSEWHICH(1)