Sponsored Content
Top Forums Shell Programming and Scripting Use positional parameters in loop / while syntax in whiptail Post 303021911 by annacreek on Monday 20th of August 2018 12:00:08 PM
Old 08-20-2018
Use positional parameters in loop / while syntax in whiptail

I like to “optimize” / make more like a real program my bash script by replacing repetitious code which utilizes positional parameters.


I am having two issues I cannot solve and would appreciate some assistance with resolving them.



a) how to modify the whiptail checklist “menu” and insert it into whiptail
b) how to replace each case with common code checking only even positional parameters


Each and every choice selected is plain command hence a common function.




I did try the while / do done but it did not echo positional parameters





Code:
  
 whiptail_DEBUG_BASE_arg(){
 
 
 # BUG did not print positional parameters
 x=1
 while [ $x -le 5 ]
 do
   echo "Welcome {${x}} times"
   x=$(( $x + 1 ))
 done
 pause
 
 
 whiptail --title "$1" \
 --checklist \
 --separate-output "Choose:" 20 78 15 \
 "$2" "$3" on \
 "$4" "$5" off \
 "$6" "$7" off \
 "$8" "$9" off \
 "${10}" "${11}" off \
 "${12}" "${13}" off \
 "${14}" "${15}" off \
 "${16}" "${17}" off \
 "${18}" "${19}" off \
 "${20}" "${21}" off \
 "${22}" "${23}" off \
 "${24}" "${25}" off \
 "${10}" "${11}" off \
 "${12}" "${13}" off \
 "${14}" "${15}" off \
 "${16}" "${17}" off \
 "${18}" "${19}" off \
 "${20}" "${21}" off \
 "${22}" "${23}" off \
 "${24}" "${25}" off \
  2>results
 
 
 while read choice
 do
         case $choice in
                 $2)
                 $2   # execute command 

                ;;
                 $4)
                 $4
                 ;;
                 $6)
                 $6
                 ;;
                 $8)
                 $8
                 ;;
                 ${10})
                 ${10}
                 ;;
                 ${12})
                 ${12}
                 ;;
                 ${14})
                 ${14}
                 ;;
                 *) echo "Invalid entry!"
                 ;;
 # BUG echo "$choice"
         esac
 done < results
 pause
 
 
  p { margin-bottom: 0.1in; line-height: 115%; }

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Positional Parameters

HPUX11.0/Korn Shell I have an old script that takes in a series of arguments when its called. The script is really more of a common set of functions that gets called by other scripts as needed. I have been asked to make this into a menu driven script to rollout to app support for their use during... (2 Replies)
Discussion started by: google
2 Replies

2. UNIX for Dummies Questions & Answers

Positional Parameters

Hello, I am using the Bourne shell. I am trying to understand the concept of positional parameters. I do understand that positional parameters: 1. Are initialized by shell 2. Have a max of 9 parameters ($1 to $9) 3. Have no limit on the number of arguments 4. Can be rearranged... (15 Replies)
Discussion started by: ericelysia
15 Replies

3. UNIX for Dummies Questions & Answers

Positional parameters

I need to get file names from commandline arguments, it may be any no of arguements, Using for loop i got but how do i display it, bcoz $i will give the number i is assigned $$i is not working either $($i), i need the names of the files got in the arguement (2 Replies)
Discussion started by: shalu@ibm
2 Replies

4. Shell Programming and Scripting

Resetting the Positional parameters values

Hi, Can any one provide the Unix command to reset the positional parameters? Please see the below example where i have to pass 2 parameters to Shell1.sh. Step1) . ./Shell1.sh 2 3 successfully executed, Then i executed(next step only) the same shell script again,this time no... (4 Replies)
Discussion started by: nmk
4 Replies

5. UNIX for Dummies Questions & Answers

Positional Parameters

Can someone tell me in more layman's terms what positional parameters are and give a good example? My book again is confusing me. :confused: (1 Reply)
Discussion started by: Straitsfan
1 Replies

6. Shell Programming and Scripting

checking the positional parameters

Hi all, I have one small requirment... I have prepared one script. we have to pass two possitional parameters to the script. What I want to do is if the parameters are not passed then i dont want the script to start the process... For ex: $ ./a.sh parm1 parm2 #Here, it can start... (7 Replies)
Discussion started by: raghu.iv85
7 Replies

7. Shell Programming and Scripting

Bash Positional Parameters Question

In a Bash script I used getopts command to let a user does something regards to the selected options. The question is: How do you find out what is the name of the file that user inserted in the command line like the following: The good part is this file is always the last argument in the... (2 Replies)
Discussion started by: bashily
2 Replies

8. Homework & Coursework Questions

Positional Parameters Shell Scripting

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: STEP 1: Create a Bash shell script (myscript) inside the a2 directory. The script should allow the user to pass... (3 Replies)
Discussion started by: tazb
3 Replies

9. UNIX for Beginners Questions & Answers

'sed' with Positional Parameters

I'm new with 'sed' and for sure something still I don't understand yet with it. If you see my output on ">Output..." portion, the new directory still on "source_dir" instead of "dest_dir". You may disregard for the "tar" part, this is just a test script, just for me to understand 'sed' using the... (3 Replies)
Discussion started by: daryl0505
3 Replies

10. UNIX for Beginners Questions & Answers

Positional parameters in if statement

I am trying to code an if statement that accepts two parameters and see if those parameters are in another file called teledir.txt. If it already exists in the file, it is to say "Entry Exists". If not, I add it to the file and say "Entry Added". This is the code I have so far: if ; then ... (1 Reply)
Discussion started by: Eric7giants
1 Replies
WHIPTAIL(1)						      General Commands Manual						       WHIPTAIL(1)

NAME
whiptail - display dialog boxes from shell scripts SYNOPSIS
whiptail [ --title title ] [ --backtitle backtitle ] [ --clear ] [ --default-item string ] [ --defaultno ] [ --fb ] [ --nocancel ] [ --yes-button text ] [ --no-button text ] [ --ok-button text ] [ --cancel-button text ] [ --noitem [ ] --output-fd fd ] [ --separate-output ] [ --scrolltext ] [ --topleft ] box-options DESCRIPTION
whiptail is a program that will let you present a variety of questions or display messages using dialog boxes from a shell script. Cur- rently, these types of dialog boxes are implemented: yes/no box, menu box, input box, message box, text box, info box, checklist box, radiolist box gauge box, and password box. OPTIONS
--clear The screen will be cleared to the screen attribute on exit. This doesn't work in an xterm (and descendants) if alternate screen switching is enabled, because in that case slang writes to (and clears) an alternate screen. --defaultno The dialog box will open with the cursor over the No button. --default-item string Set the default item in a menu box. Normally the first item in the box is the default. --fb, --fullbuttons Use full buttons. (By default, whiptail uses compact buttons). --nocancel The dialog box won't have a Cancel button. --yes-button text Set the text of the Yes button. --no-button text Set the text of the No button. --ok-button text Set the text of the Ok button. --cancel-button text Set the text of the Cancel button. --noitem The menu, checklist and radiolist widgets will display tags only, not the item strings. The menu widget still needs some items spec- ified, but checklist and radiolist expect only tag and status. --notags Don't display tags in the menu, checklist and radiolist widgets. --separate-output For checklist widgets, output result one line at a time, with no quoting. This facilitates parsing by another program. --output-fd fd Direct output to the given file descriptor. Most whiptail scripts write to standard error, but error messages may also be written there, depending on your script. --title title Specifies a title string to be displayed at the top of the dialog box. --backtitle backtitle Specifies a backtitle string to be displayed on the backdrop, at the top of the screen. --scrolltext Force the display of a vertical scrollbar. --topleft Put window in top-left corner. -h, --help Print a help message and exit. -v, --version Print version information and exit. Box Options --yesno text height width A yes/no dialog box of size height rows by width columns will be displayed. The string specified by text is displayed inside the dialog box. If this string is too long to be fit in one line, it will be automatically divided into multiple lines at appropriate places. The text string may also contain the sub-string " " or newline characters ` ' to control line breaking explicitly. This dialog box is useful for asking questions that require the user to answer either yes or no. The dialog box has a Yes button and a No button, in which the user can switch between by pressing the TAB key. --msgbox text height width A message box is very similar to a yes/no box. The only difference between a message box and a yes/no box is that a message box has only a single OK button. You can use this dialog box to display any message you like. After reading the message, the user can press the ENTER key so that whiptail will exit and the calling shell script can continue its operation. --infobox text height width An info box is basically a message box. However, in this case, whiptail will exit immediately after displaying the message to the user. The screen is not cleared when whiptail exits, so that the message will remain on the screen until the calling shell script clears it later. This is useful when you want to inform the user that some operations are carrying on that may require some time to finish. --inputbox text height width [init] An input box is useful when you want to ask questions that require the user to input a string as the answer. If init is supplied it is used to initialize the input string. When inputing the string, the BACKSPACE key can be used to correct typing errors. If the input string is longer than the width of the dialog box, the input field will be scrolled. On exit, the input string will be printed on stderr. --passwordbox text height width [init] A password box is similar to an input box, except the text the user enters is not displayed. This is useful when prompting for pass- words or other sensitive information. Be aware that if anything is passed in "init", it will be visible in the system's process ta- ble to casual snoopers. Also, it is very confusing to the user to provide them with a default password they cannot see. For these reasons, using "init" is highly discouraged. --textbox file height width A text box lets you display the contents of a text file in a dialog box. It is like a simple text file viewer. The user can move through the file by using the UP/DOWN, PGUP/PGDN and HOME/END keys available on most keyboards. If the lines are too long to be displayed in the box, the LEFT/RIGHT keys can be used to scroll the text region horizontally. For more convenience, forward and backward searching functions are also provided. --menu text height width menu-height [ tag item ] ... As its name suggests, a menu box is a dialog box that can be used to present a list of choices in the form of a menu for the user to choose. Each menu entry consists of a tag string and an item string. The tag gives the entry a name to distinguish it from the other entries in the menu. The item is a short description of the option that the entry represents. The user can move between the menu entries by pressing the UP/DOWN keys, the first letter of the tag as a hot-key. There are menu-height entries displayed in the menu at one time, but the menu will be scrolled if there are more entries than that. When whiptail exits, the tag of the chosen menu entry will be printed on stderr. --checklist text height width list-height [ tag item status ] ... A checklist box is similar to a menu box in that there are multiple entries presented in the form of a menu. You can select and deselect items using the SPACE key. The initial on/off state of each entry is specified by status. On exit, a list of the tag strings of those entries that are turned on will be printed on stderr. --radiolist text height width list-height [ tag item status ] ... A radiolist box is similar to a menu box. The only difference is that you can indicate which entry is currently selected, by set- ting its status to on. --gauge text height width percent A gauge box displays a meter along the bottom of the box. The meter indicates a percentage. New percentages are read from standard input, one integer per line. The meter is updated to reflect each new percentage. If stdin is XXX, the first following line is a percentage and subsequent lines up to another XXX are used for a new prompt. The gauge exits when EOF is reached on stdin. NOTES
whiptail interprets arguments starting with a dash "-" as being arguments. To avoid this, and start some text in, for example, a menubox item, with a dash, whiptail honours the getopt convention of accepting the special argument "--" which means that all following arguments with dashes are to be treated verbatim and not parsed as options. DIAGNOSTICS
Exit status is 0 if whiptail is exited by pressing the Yes or OK button, and 1 if the No or Cancel button is pressed. Otherwise, if errors occur inside whiptail or whiptail is exited by pressing the ESC key, the exit status is -1. AUTHOR
Based on the man page for dialog(1) by: Savio Lam (lam836@cs.cuhk.hk) - version 0.3 Stuart Herbert (S.Herbert@sheffield.ac.uk) - patch for version 0.4 Modifications for whiptail by: Enrique Zanardi (ezanard@debian.org) Alastair McKinstry (mckinstry@debian.org) Whiptail Version 0.52.5 31 January 2007 WHIPTAIL(1)
All times are GMT -4. The time now is 06:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy