04-11-2019
In post #5 in this thread drl gave you two scripts and showed you the output the first script produced when it was run after the second script had been installed under the name my-hilite.
It seems that wisecracker installed those two scripts on his system naming the first script Colour_test.sh and naming the second script my-hilite. When wisecracker ran Colour_test.sh it produced the output that drl showed us in post #5 and that wisecracker showed us again in post #16. I also installed those two scripts on my system with the same names that wisecracker used, and when I ran Colour_test.sh it also produced the output that drl showed us in post #5.
We are all having a hard time understanding how you installed two files named my-hilite in the same directory. But, if you had installed what we are calling Colour_test.sh in a file named my-hilite and invoked it with the name my-hilite that would indeed produce the output you showed us since that script was very busy calling itself until you exceeded the number of processes your operating system allowed to to run concurrently.
This User Gave Thanks to Don Cragun For This Post:
2 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I am using RHEL 6.1 on VMware
I am searching for a way to change background color (not line by line color wich one can using tput command)
basically changing the color of the whole screen to white instead of the default black and changing font color to black and alos would like to... (2 Replies)
Discussion started by: Dexobox
2 Replies
2. UNIX for Beginners Questions & Answers
hi Folks,
Can anyone help with changing the color of the words in a linux shell script?
I get how to change default background etc in putty, but for some reason the text in the script has different colors for different parts of the cript.
Is there a way to have one color in a linux shell... (5 Replies)
Discussion started by: jonnyd
5 Replies
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)