07-25-2006
getopt is useful when there is a need to parse command line arguments and in this case it would not work.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
need a script that goes something like this
#!/usr/bin/bash
echo "input up to TEN values, separated by spaces"
read vari1 vari2 vari3 vari4 vari5 vari6 vari7 vari8 vari9 vari10
#set null variables to 9999 (somehow?)
#now echo all variables
echo $vari1 $vari2 $vari3 $vari4 $vari5 $vari6... (1 Reply)
Discussion started by: ajp7701
1 Replies
2. Shell Programming and Scripting
Hello;
Please I need to read inputs from a file change 1 or 2 things the output to another file. (1 Reply)
Discussion started by: jimoney
1 Replies
3. Programming
I was wondering if its possible to read mouse inputs using ioctl functions somehow ? If it is not too much of trouble can anyone write or even direct me to sample code of ioctl reading someother HID. (2 Replies)
Discussion started by: maverick_
2 Replies
4. UNIX for Dummies Questions & Answers
- A=90-100
- B=80-89
- C=70-79
- D=60-69
- F=0-59.
echo -n "What test score did you get? (0-100)"
read score1
echo “you got a $score1”
if
. then
echo “you got a F”
else
echo
---------------------
) echo you got... (2 Replies)
Discussion started by: JudoMan
2 Replies
5. UNIX for Dummies Questions & Answers
Hello Everyone.
I am trying to display contains of a file from a specific line to a specific line(let say, from line number 3 to line number 5). For this I got the shell script as shown below:
if ; then
if ; then
tail +$1 $3 | head -n $2
else
... (5 Replies)
Discussion started by: grc
5 Replies
6. Programming
i used a two-way linked list "node" for the code::
#include<stdio.h>
#include<malloc.h>
void insert();
void reverse();
struct node
{
char c;
struct node *next;
struct node *back;
}*start=NULL;
int main()
{
int n,i; (4 Replies)
Discussion started by: mscoder
4 Replies
7. Shell Programming and Scripting
Hello everyone,
I don't really know anything about scripting, but I have to manage to make this script, out of necessity.
#!/bin/bash
while read -r line; do #I'm reading from a big wordlist
instructions using $line
done
Is there a way to automatically write the $line number the script... (4 Replies)
Discussion started by: bobylapointe
4 Replies
8. Shell Programming and Scripting
I am trying to make an interactive script. Only problem my inputs are not read and correctly channeled.
Please help:
Here is my code
#!/bin/sh
PATHSCRIPT=/home/pp/tmp
#if ; then
# echo "Syntax : $0 input off lat sample"
# exit 1
# fi
echo "Choice of Graph"
echo "1 -- Type... (5 Replies)
Discussion started by: newkid.7955
5 Replies
9. Shell Programming and Scripting
Hello,
I am new to awk and I am trying to figure out how to print an output based on user input.
For example:
ubuntu:~/scripts$ steps="step1, step2, step3"
ubuntu:~/scripts$ echo $steps
step1, step2, step3
I am playing around and I got this pattern that I want:
... (3 Replies)
Discussion started by: tattoostreet
3 Replies
10. UNIX for Beginners Questions & Answers
Say I have this line:
read -p "Enter 3 numbers: " num1 num2 num3;
I want to write a while loop that repeatedly asks for input if the number of inputs entered is not equal to 3.
I don't know the correct command to find the number of inputs entered. Help, please? (4 Replies)
Discussion started by: jejemonx
4 Replies
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