10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi everybody,
I'm trying to use a foreach command with two lists. The file.txt looks like this:
var1: 100 200 300
var2: 3 6 9
I'm trying to use a foreach command to associate the two variables together. My script looks like this:
#! /bin/tcsh
set a=(`cat file.txt | grep 'var1' | cut -d... (8 Replies)
Discussion started by: SimonWhite
8 Replies
2. Shell Programming and Scripting
I have a foreach loop in a csh script and I noticed that it tries to find the files with the pattern *$searchpt* in the file name. I'm confused as I never specified checking for the files.
foreach f ( *$searchpt* )
set fnew = `echo $f | awk -v searchpat=$searchpt \
... (1 Reply)
Discussion started by: kristinu
1 Replies
3. Shell Programming and Scripting
I have a simple csh script that has a simple foreach loop that goes over numbers, from 1 to 10:
foreach n(1 2 3 4 5 6 7 8 9 10)
...
end
Now I want to expand the script to work on over a hundred consecutive n values. Obviously, typing all the numbers between 1 to 100 is an unreasonable... (7 Replies)
Discussion started by: mcbenus
7 Replies
4. UNIX for Dummies Questions & Answers
OK, so I am extremely rusty and am just getting back to Unix after 9 years.
I'm stuck on something easy. I want to search line-by-line for a string in a file, and I want to do this to a series of files in a directory.
This works fine to do the search:
while read i; do grep $i file2; done... (3 Replies)
Discussion started by: moldoverb
3 Replies
5. Shell Programming and Scripting
Hi everyone
Does anyone know what is wrong with this script. i keep getting errors
foreach filename (`cat testing1`)
set string=$filename
set depth=`echo "$string"
echo $depth
end
the error is the following
testing: line 1: syntax error near unexpected token `('
testing: line 1:... (3 Replies)
Discussion started by: ROOZ
3 Replies
6. Shell Programming and Scripting
Hi Guys,
I have a loop which uses a wildcard
i.e. foreach f (*)
but when I execute the tcsh file in unix then it gives me an error
->>>>>>>foreach: words not parenthesized<<<<<<<<<<-
Any help. (1 Reply)
Discussion started by: abch624
1 Replies
7. Shell Programming and Scripting
What am I doing wrong with this foreach loop?
foreach var ($argv)
@sum = $sum + $var (4 Replies)
Discussion started by: haze21
4 Replies
8. Shell Programming and Scripting
Hi,
I'm having a small issue here and I can't get it to work. I'm programming a script for bash and I need to do something to all the folder in a directory. So I'm in the directory and I want to use the foreach statement but I dont know how to reference all the folders of that directory. To make... (7 Replies)
Discussion started by: eltinator
7 Replies
9. Shell Programming and Scripting
#!/bin/bash
foreach x (67402996 67402998)
{
grep -a x FINAL2006.dat >> MISSING_RECORDS.dat
}
I'm trying to pass a list to the variable x, and then grep for that string in FINAL2006.dat...
Final2006.dat is in the same folder as my .sh file. I call this with a .cmd file...
At any rate,... (6 Replies)
Discussion started by: JimWork
6 Replies
10. UNIX for Dummies Questions & Answers
SaLAam
What is the best way to change a word withing a files name. I know I'm not clear enough I will give example : -
I have in /test/test N number of files like this
1662_WAITING
1666_WAITING
1670_DONE
1678_DONE
1663_WAITING
1667_WAITING
1673_WAITING ... (5 Replies)
Discussion started by: geoquest
5 Replies
shell_builtins(1) shell_builtins(1)
NAME
shell_builtins, case, for, foreach, function, if, repeat, select, switch, until, while - shell command interpreter built-in commands
The shell command interpreters csh(1), ksh(1), and sh(1) have special built-in commands. The commands case, for, foreach, function, if,
repeat, select, switch, until, and while are commands in the syntax recognized by the shells. They are described in the Commands section of
the manual pages of the respective shells. The remaining commands listed in the table below are built into the shells for reasons such as
efficiency or data sharing between command invocations. They are described on their respective manual pages.
|
Command | Shell
alias |csh, ksh
bg |csh, ksh, sh
break |csh, ksh, sh
case |csh, ksh, sh
cd |csh, ksh, sh
chdir |csh, sh
continue |csh, ksh, sh
dirs |csh
echo |csh, ksh, sh
eval |csh, ksh, sh
exec |csh, ksh, sh
exit |csh, ksh, sh
export |ksh, sh
false |ksh
fc |ksh
fg |csh, ksh, sh
for |ksh, sh
foreach |csh
function |ksh
getopts |ksh, sh
glob |csh
goto |csh
hash |ksh, sh
hashstat |csh
history |csh
if |csh, ksh, sh
jobs |csh, ksh, sh
kill |csh, ksh, sh
let |ksh
limit |csh
login |csh, ksh, sh
logout |csh, ksh, sh
nice |csh
newgrp |ksh, sh
nohup |csh
notify |csh
onintr |csh
popd |csh
print |ksh
pushd |csh
pwd |ksh, sh
read |ksh, sh
readonly |ksh, sh
rehash |csh
repeat |csh
return |ksh, sh
select |ksh
set |csh, ksh, sh
setenv |csh
shift |csh, ksh, sh
source |csh
stop |csh, ksh, sh
suspend |csh, ksh, sh
switch |csh
test |ksh, sh
time |csh
times |ksh, sh
trap |ksh, sh
true |ksh
type |ksh, sh
typeset |ksh
ulimit |ksh, sh
umask |csh, ksh, sh
unalias |csh, ksh
unhash |csh
unlimit |csh
unset |csh, ksh, sh
unsetenv |csh
until |ksh, sh
wait |csh, ksh, sh
whence |ksh
while |csh, ksh, sh
Bourne Shell, sh, Special Commands
Input/output redirection is now permitted for these commands. File descriptor 1 is the default output location. When Job Control is
enabled, additional Special Commands are added to the shell's environment.
In addition to these built-in reserved command words, sh also uses:
: No effect; the command does nothing. A zero exit code is returned.
.filename Read and execute commands from filename and return. The search path specified by PATH is used to find the directory con-
taining filename.
C shell, csh
Built-in commands are executed within the C shell. If a built-in command occurs as any component of a pipeline except the last, it is exe-
cuted in a subshell. In addition to these built-in reserved command words, csh also uses:
: Null command. This command is interpreted, but performs no action.
Korn Shell, ksh, Special Commands
Input/Output redirection is permitted. Unless otherwise indicated, the output is written on file descriptor 1 and the exit status, when
there is no syntax error, is zero.
Commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
In addition to these built-in reserved command words, ksh also uses:
* : [ arg ... ] The command only expands parameters.
* .file [ arg ..Read the complete file then execute the commands. The commands are executed in the current shell environment. The search
path specified by PATH is used to find the directory containing file. If any arguments arg are given, they become the posi-
tional parameters. Otherwise, the positional parameters are unchanged. The exit status is the exit status of the last com-
mand executed. the loop termination test.
intro(1), alias(1), break(1), cd(1), chmod(1), csh(1), echo(1), exec(1), exit(1), find(1), getoptcvt(1), getopts(1), glob(1), hash(1), his-
tory(1), jobs(1), kill(1), ksh(1), let(1), limit(1), login(1), logout(1), newgrp(1), nice(1), nohup(1), print(1), pwd(1), read(1), read-
only(1), set(1), sh(1), shift(1), suspend(1), test(1B), time(1), times(1), trap(1), typeset(1), umask(1), wait(1), chdir(2), chmod(2),
creat(2), umask(2), getopt(3C), profile(4), environ(5)
29 Jun 2005 shell_builtins(1)