Bash: Reading 2 arguments from a command line

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Wanted: Help with escaping bash command line arguments

Please forgive me if this is the wrong forum. I want to execute some one liners with the groovy programming language and I'm having trouble escaping the special characters to accommodate bash. Here is one of the lines that is giving me trouble: groovy -e "(new...

2. Programming

Reading command line arguments and setting up values if option not provided

I have a C++ program. I read command line arguments, but if the value is not supplied, I default or make a calculation. Let's say I set it to a default value. I can code this in several ways. Here I show three ways. What would be the best way for maintaining this code? The program will get very...

3. Shell Programming and Scripting

Reading command line options from bash script

I have the following code and I am calling it using ./raytrac.bash -u and getting problems. For some reason opt_usage is still 0. opt_usage=0 iarg=0 narg=$# while (($iarg < $narg)) do (( iarg = $iarg + 1 )) arg=$argv usrInputFlag=`echo $arg | awk '/=/ {print 1}; ! /=/...

4. UNIX for Dummies Questions & Answers

Accepting command line arguments in bash

I have this tcsh code that I want to convert to a bash script. Basically it accepts command line arguments supplied by the user and stores them, so they can be used to run a C++ program. set arg_browseDir_inFileLst = "" set allArgsUpCase = `echo "$*" | tr '' ''` set opt_browseDir_flag =...

5. Shell Programming and Scripting

Passing arguments from a bash shell script to a command

I'm pretty new to bash scripting and I've found myself writing things like this (and the same with even more nesting): if $CATEGORIES; then if $LABEL_SLOTS; then $pyth "$wd/texify_grammar.py" "$input" "$texfile" "--label-slots" "--categories" "$CATEGORY_LIST" ...

6. UNIX for Dummies Questions & Answers

command line arguments

hi, can someone how to accept command line arguments as a variable using in script? like: ./scriptname arguments by accept arguments, I can use it in my script? thx!

7. Shell Programming and Scripting

Help parsing command line arguments in bash

Looking for a little help parsing some command line arguments in a bash script I am working on, this is probably fairly basic to most, but I do not have much experience with it. At the command line, when the script is run, I need to make sure the argument passed is a file, it exists in the...

8. UNIX for Dummies Questions & Answers

Command line arguments.

I am working on a script wherein i need the user to enter the Build ID for eg:the command line will show enter the build ID Now on entering the build ID it should be assigned to @ARGV. How can this be done.?

9. Shell Programming and Scripting

command line arguments

-------------------------------------------------------------------------------- I have this while loop and at the end I am trying to get it to tell me the last argument I entered. And with it like this all I get is the sentence with no value for $1. Now I tried moving done after the sentence...

10. Programming

command line arguments

Hi How to pass multi line text as a command line argument to a program. (i.e) ./a.out hi this is sample 0 file1 where hi this is sample should be stored in argv 0 in argv and so on...

LEARN ABOUT FREEBSD

getopt

GETOPT(1)						    BSD General Commands Manual 						 GETOPT(1)

NAME

     getopt -- parse command options

SYNOPSIS

     args=`getopt optstring $*` ; errcode=$?; set -- $args

DESCRIPTION

     The getopt utility is used to break up options in command lines for easy parsing by shell procedures, and to check for legal options.
     Optstring is a string of recognized option letters (see getopt(3)); if a letter is followed by a colon, the option is expected to have an
     argument which may or may not be separated from it by white space.  The special option '--' is used to delimit the end of the options.  The
     getopt utility will place '--' in the arguments at the end of the options, or recognize it if used explicitly.  The shell arguments ($1 $2
     ...) are reset so that each option is preceded by a '-' and in its own shell argument; each option argument is also in its own shell argu-
     ment.

EXIT STATUS

     The getopt utility prints an error message on the standard error output and exits with status > 0 when it encounters an option letter not
     included in optstring.

EXAMPLES

     The following code fragment shows how one might process the arguments for a command that can take the options -a and -b, and the option -o,
     which requires an argument.

	   args=`getopt abo: $*`
	   # you should not use `getopt abo: "$@"` since that would parse
	   # the arguments differently from what the set command below does.
	   if [ $? -ne 0 ]; then
		   echo 'Usage: ...'
		   exit 2
	   fi
	   set -- $args
	   # You cannot use the set command with a backquoted getopt directly,
	   # since the exit code from getopt would be shadowed by those of set,
	   # which is zero by definition.
	   while true; do
		   case "$1" in
		   -a|-b)
			   echo "flag $1 set"; sflags="${1#-}$sflags"
			   shift
			   ;;
		   -o)
			   echo "oarg is '$2'"; oarg="$2"
			   shift; shift
			   ;;
		   --)
			   shift; break
			   ;;
		   esac
	   done
	   echo "single-char flags: '$sflags'"
	   echo "oarg is '$oarg'"

     This code will accept any of the following as equivalent:

	   cmd -aoarg file file
	   cmd -a -o arg file file
	   cmd -oarg -a file file
	   cmd -a -oarg -- file file

SEE ALSO

     getopts(1), sh(1), getopt(3)

HISTORY

     Written by Henry Spencer, working from a Bell Labs manual page.  Behavior believed identical to the Bell version.	Example changed in FreeBSD
     version 3.2 and 4.0.

BUGS

     Whatever getopt(3) has.

     Arguments containing white space or embedded shell metacharacters generally will not survive intact; this looks easy to fix but is not.  Peo-
     ple trying to fix getopt or the example in this manpage should check the history of this file in FreeBSD.

     The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of
     getopt; this again is hard to fix.

     The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell ver-
     sion to another.

     Each shellscript has to carry complex code to parse arguments halfway correctly (like the example presented here).  A better getopt-like tool
     would move much of the complexity into the tool and keep the client shell scripts simpler.

BSD
								 January 26, 2011							       BSD

Shell Programming and Scripting