Actually I wanted to incorporate more options to this script, so I'm trying to use the getopts. My requirement is apart from the numeral values I want to check for other options.
That's what i understood.
Therefore, the shift $(($OPTIND - 1)) command sets the first parameter after the options as $1, no matter the number of options.
You must call the script with the usual syntax like
I have a script which fires a command based on certain parameters. I am posting the code below..
The options needs be given such that
-u option goes along with -d and -s, -f goes with -d and -t goes with -s and -d.
1) How do I ensure that user misses any of the option then he should be... (5 Replies)
hey
need help with getopts again.
i am using getopts to read my command line options and arguments. i can manage to do for options that have only one argument
e.g srcipt_name -f 3
i am able to use getopts to do this but i am having problems two accept more than two agruments
e.g.... (1 Reply)
Is there a restriction on levels of using 'getopts' ? I have several scripts, each of which requires an option as the first parameter .
If I call one prg separately it works fine, but when one prg calls another prg and passes the option on the called prg, then the called prg
seems not to process... (3 Replies)
I am having some trouble/questions with getopts that I can't find any solid info on with google
I need it to parse things of the syntax of:
-r # # # -f -c
with as many repeats as possible, and it should catch erroneous commands also, but continue going...
my first question is, -r... (3 Replies)
First off, I apologize for my lack of knowledge. I realize my problem will probably seem pretty basic to everyone, but I've been at this for several hours now and I've gotten nowhere. I would contact my professor, but it is too late for that.
Anyway, I'm trying to write a function called... (1 Reply)
I have an for loop that reads the following file
cat param.cfg
val1:env1:opt1
val2:env2:opt2
val3:env3:opt3
val4:env4:opt4
.
.
The for loop extracts the each line of the file so that at any one point, the value of i is
val1:env1:opt1 etc...
I would like to extract each... (19 Replies)
while getopts v OPTION
do
case $OPTION in
v) echo "Hello" ;;
*) exit 1;;
esac
done
Suppose I have script tmp.sh
Whose Signature is tmp.sh <fixed_argument>
When I run the script with tmp.sh -v "file", it echoes a hello but, when I try the other way i.e, tmp.sh... (1 Reply)
Hi All,
I am writing a script to pass the getopts argument to the function which I have. But it as soon as I execute the script, the argument is taking it as blank. I tried using multiple way to check but its not working.
Can someone please let me know what wrong in this code.
function1()... (4 Replies)
Discussion started by: sidh_arth85
4 Replies
LEARN ABOUT DEBIAN
colorgccrc
COLORGCCRC(5) File Formats Manual COLORGCCRC(5)NAME
colorgccrc - configuration file for colorgcc
DESCRIPTION
A colorgccrc configuration file is used to configure the highlighting of the compiler output from colorgcc.
SYNTAX
Each line consists of a keyword designating a configuration variable. The keyword is followed by `:' and then one or several values
(depending on the keyword). Lines beginning with a hash mark `#' are comments.
CONFIGURATION VARIABLES
g++ | gcc | c++ | cc | g77 | gcj | gnat | gpc
Specifies the paths to the compilers. Takes one value; a path to the compiler.
nocolor
Specifies what terminal types colorization should be disabled on. Takes one or several values, separated by whitespace.
srcColor
Specifies the highlighting attributes source-code should be given. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
introColor
Specifies the highlighting attributes for normal compiler output. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
warningFileNameColor | errorFileNameColor
Specifies the highlighting attributes for the filename in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningNumberColor | errorNumberColor
Specifies the highlighting attributes for the line-number in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningMessageColor | errorMessageColor
Specifies the highlighting attributes for the message-text in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
COLOR ATTRIBUTES
The following attributes are valid for highlighting.
clear, reset
bold, underline, underscore, blink, reverse, concealed
black, red, green, yellow, blue, magenta, cyan, white
on_black, on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, on_white
SEE ALSO gcc(1), colorgcc(1)HISTORY
Jan 15 2003: Initial version of this manual-page.
REPORTING BUGS
Report bugs to <jmoyers@geeks.com>
AUTHORS
Jamie Moyers <jmoyers@geeks.com> is the author of colorgcc.
This manual page was written by Joe Wreschnig <piman@sacredchao.net>, and modified by David Weinehall <tao@debian.org>, for the Debian
GNU/Linux system (but may be used by others).
COPYRIGHT
Copyright (C) 2003 Jamie Moyers
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Jan 15, 2003 COLORGCCRC(5)