Thank you for explaining that to me. The currently working script is as follows:
Code:
#!/bin/bash
win=no
echo "Please pick a number"
read number
while [ $win = no ]; do
if [ -z $number ]; then
echo "Please input a number"
win=no
read number
elif [[ "$number" == +([0-9]) ]]; then
echo "That is a number, Good Job!"
win=yes
elif [[ $number == +([[:alnum:]]) ]]; then
echo "That is not a number"
win=no
echo "Please input a number"
read number
fi
done
Thanks again for the help!
Last edited by vgersh99; 12-10-2018 at 12:22 PM..
Reason: Code tags, please!
hi!
i need to do a ksh script that uses a wile loop that is fed form below
while read line
do
some things
done < myfile
inside the while loop i need to read user input to ask the user what he wants to do, but "read" reads the file, and not the standard input
while read line
do
... (2 Replies)
Hello, i know how to retrieve a user input (read), and how to manage the different options (case statement).
But... could anybody show me a script that, if the user option is incorrect, don't allow to continue the excution, i.e., if the value entered is not 1 or 2, the script shows a question.
... (2 Replies)
Hello everybody!!!
I am writing my own rm command in unix.
I prompt the user to type if he wants to delete a file and then read what he typed.
But how do i check what he typed?
This is my program so far:
echo 'Delete prog1.c (y/n)?'
read yesOrNo
if yesOrNo == 'y'
then
rm prog1.c... (6 Replies)
I'm new to BASH and i'm trying to create a script which is simply put a large find and replace file. This is what I have so far
N=0
while read LINE ; do
N=$((N+1))
sed 's/'$2'/'$3'/g' $LINE > .temp
echo "Changes to file $N = $LINE"
echo 'The following changes... (5 Replies)
until
do
read -p "Invalid cars. Try againa" cars1
done
Ok i have the above code, im getting users input and if it doesnt match in the file the user has to try again untill its correct
But when i run this it gives me an error saying
./Cars.bash: line 43: (2 Replies)
Good Evening. I'm new to C. Can you please help me.
I'm creating an error checking function, user will input a string, this will check if the input is all alphabet or all letters only. If there is a digit or other special char, it will print Error then ask input from user again.
Here's my... (1 Reply)
Hi,
I need my script to check if the user enters 3 values if not 5 values to my script and alert if the input has any other number of values.
for example:
./myscript.sh 22 56 3221 - > correct
./myscript.sh 22 56 3221 45 777 -> correct
./myscript.sh 22 56 3221 45 -> incorrect
Please... (6 Replies)
I have a shell script, and its pretty much done, I decided to add a loop that ends or continues depending on user input. like "would you like to continue?" and if I hit y or yes it will run the loop again until I hit n or no and breaks out of the loop.
To be hones I didn't think I needed to add... (2 Replies)
Hi,
On my Java webpage which invokes the shell script has two checkboxes viz ...
apache
and
weblogic
apache require one parameter i.e apache home from the user while Weblogic requires three or five params from the user vi.z weblogic_home or <jdk_home, config_home & pid>, username and... (4 Replies)
How to check the user input to be valid using shell script?
The valid input is in the format like as follows.
1. It can only have r,w,x or a hyphen and nothing else.
2. ensure the r, w, x are in the correct order.
for example: rwxr-xr-x is a valid format.
Thanks (5 Replies)
Discussion started by: hyeewang
5 Replies
LEARN ABOUT LINUX
win
win(1) General Commands Manual win(1)NAME
win - Terminal emulator
SYNOPSIS
win [-v] [-t name] [command [argument ...]] address
OPTIONS -v If the -v option is present, win prints its version number and date and exits.
-tname If the -t option is present, win uses +name as the final part of the tag name of its window.
DESCRIPTION
win must be able to connect to a running wily(1). win attaches to a window. If the -t option is present, the final part of the tag name
is name. If command is present, the final part of the tag name is +command. Otherwise, the final part of the tag name is +win. The first
part of the tag name is the current working directory.
win runs a program in a child process. The child process is the leader of a process group and is connected to win by a pseudo-terminal.
If command is specified, the child process runs
$SHELL -c 'command argument ...'
otherwise it runs
$SHELL -i
If SHELL is not found in the environment, /bin/sh is used.
TERM=win is placed in the environment of the running program.
Output from the running command appears in the window. The point after the last output from the running command is known as the output
point. Further output from the running command appears just before the output point. The output point is initially at the end of the win-
dow.
Normal wily editing commands work in the window. When a newline, interrupt character, or end-of-file character is created after the output
point, the text between the output point and the last newline, interrupt character, or end-of-file character in the window (inclusive) is
passed to the running program as input.
The interrupt character is control-C and the end-of-file character is control-D. The pseudo-terminal initially is configured so that these
are recognized with their normal meanings.
The B2 commands beginning with the |, <, or > characters or an upper case letter are executed normally by wily. Other B2 are first termi-
nated with a newline, if they are not already, and are then appended to the buffer (and thereafter passed to the running program).
RETURNS
win returns zero if it is able to successfully create the child process, otherwise it returns non-zero.
EXAMPLES
Run a terminal emulator within wily
win
Run FTP within wily
win ftp
Run rlogin within wily
win -t host.domain rlogin -8 host.domain
SEE ALSO wily(1)Tag(1)Man(1)BUGS
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the
interrupt and eof characters.
rlogin seems to need -8 and, annoyingly, sets echo and onlcr. The latter can be fixed in your .rcrc:
if ( ~ $TERM win ) {
stty -echo -onlcr
}
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the
interrupt and eof characters.
WEdestroy messages aren't yet passed by wily. Thus, Del and Delcol can delete the window yet leave win running.
There is a race condition; the user can press newline and then delete text before win has a chance to read it.
AUTHOR
win was originally written by Gary Capell (gary@cs.su.oz.au). Alan Watson (alan@oldp.nmsu.edu) rewrote it and added support for arguments,
pseudo-terminals instead of pipes, and execution of certain B2 commands by wily. The pseudo-terminal support in 9term, written by Matty
Farrow (matty@cs.su.oz.au), was a great help.
1R1.1L1 of 1D1 win(1)