Footnote: For anybody following this thread, this is a discussion thread.
@jgt is expert and definitely did not ask this question.
I must confess that I was confused until that footnote clued me in to the fact that I wasn't in the shell scripting forum anymore (got here via the 'new posts' link).
Quote:
Originally Posted by methyl
Until looking at unix.com I had never seen the for var in <open-ended list> construct ever ... and still wonder which course/manual/book/rumour it comes from?
I don't know for certain, but my first impulse is to blame GNU Bash. I've seen that idiom recommended as the correct way to work around the fact that the final command in a bash pipeline runs in a subshell.
From the Advanced Bash-Scripting Guide's Bash Gotchas:
Regards,
Alister
hi all,
Can any 1 help me translate this korn shell code to C shell code :
email=$(grep "^$1" $folder/config_2.txt | awk '{print $2'})
In config_2.txt the content is :
which mean in korn shell , $1=groupname and $2=email address.
Now i need to write in C shell script,when i set the... (2 Replies)
Hi,
I want to remove the following code from Source files (or replace the code with empty.) from all the source files in given directory.
finally {
if (null != hibernateSession && hibernateSession.isOpen()) {
//hibernateSession.close();
}
}
It would be great if the script has... (2 Replies)
Hi ,
I have a code where i am using a infinite while loop . some thing like below
while
do
if
then
#go to line 20
fi
command 1;
command 2;
#line 20:
sleep 34; (5 Replies)
I have about 12,000,000 mod files I'm trying to turn into a test of "unlimited cloud storage" by running them all through VLC and blowing them into mp3 files. I can get this to work serially but when trying to use openMPI or Parallel, something in the syntax is tripping it up some. Here is an... (1 Reply)
Discussion started by: sparticus414
1 Replies
LEARN ABOUT LINUX
makesh
MAKESH(1) General Commands Manual MAKESH(1)NAME
makeSH - a .SH script maker
SYNOPSIS
makeSH files
DESCRIPTION
MakeSH examines one or more scripts and produces a .SH file that, when run under sh, will produce the original script. The .SH script so
produced has two sections containing code destined for the output. The first section has variable substitutions performed on it (taking
values from config.sh), while the second section does not. MakeSH does not know which variables you want to have substituted, so it puts
the whole script into the second section. It's up to you to insert any variable substitutions in the first section for any values you want
from config.sh.
You should run makeSH from within your top-level directory and use the relative path to the file as an argument, so that the "Extracting
..." line printed while running the produced .SH file later on will give that same path.
AUTHOR
Larry Wall <lwall@netlabs.com>
SEE ALSO pat(1), metaconfig(1), makedist(1).
BUGS
It could assume that variables from metaconfig's Glossary need to be initialized in the first section, but I'm too lazy to make it do that.
LOCAL MAKESH(1)