Can anyone please tell me why this wont work! Thanks so much!
#!/bin/sh
for file
do
case $file in
*.*.*)
echo Cannot have more than 1 dot
exit
;;
*'**'*)
echo Cannot have more than 1 asterisk
exit
;;
*'*'*|?.)
echo this is a target (19 Replies)
I want to write a program with the following variables:
a=7000
b=24000
c=613.8
The user can enter two words: Vivid or Blue for example. The challenge is that the user might not want to write the words the way they appear. The user can write V or v or vivid or Vivid or write Blue or blue, or B,... (1 Reply)
Hi all,
I think i'm asking a sqtupid question here..
i'm using case sttament, what is the syntax or symbol for "or"?
I thought was ||
here a quick sample of my case statment
echo "Would you like to update your detail ?"
read response
case $response in
... (2 Replies)
Hi,
I am writing a bash shell script. My script has a few user defined parameters. When the script runs the first thing it does is make sure that these parameters are valid. One of the parameters is called YEAR. A valid input for YEAR can be 1997-2000.
One way I have come up with to ensure... (3 Replies)
Hi,
I am writing case statement to execute some finction, my requirement is once one of the case statement is executed again it has to prompt for the option.
for script in `echo "$Script_Selected"`
do
case $script in
1) getNoOFActUsers
;;
2) moveServerrOORotation
;;
... (2 Replies)
Hello,
The standard case statement :-
case "$1" in
"IE0263")
commands;;
"IE0264")
commands;;
esac
is it possible to have :-
case "$1" in
"IE0263" OR "IE0878")
commands;;
"IE0264")
commands;;
esac
Thanks (4 Replies)
Hey, guys I really need some help with a project.
"Write a shell program that examines the command line arguments, counts and collects the number of options. Basically it has to collect and count the arguments that start with a "-" and the one's that don't start with a -
I know I have to use... (2 Replies)
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:
Hey, guys I really need some help with a project.
"Write a shell program that examines the command line... (8 Replies)
Hi I am new to shell scripting, I wanted to make a shell script that has a case statement asking the user to select their city 1)london 2)tokyo 3) etc., I then want the users input to be stored in a variable and echoed out in another script; so for example if the user selects tokyo, tokyo city code... (2 Replies)
Hi. I wrote the following case statement to replace a series of 'ELIF' statements as it looks better and is easier to maintain. However, for some reason the commands don't fully work in this format. Take option 1. It should call a script that runs in the background but it doesn't work. Can anyone... (3 Replies)
Discussion started by: user052009
3 Replies
LEARN ABOUT CENTOS
lua
LUA(1) General Commands Manual LUA(1)NAME
lua - Lua interpreter
SYNOPSIS
lua [ options ] [ script [ args ] ]
DESCRIPTION
lua is the stand-alone Lua interpreter. It loads and executes Lua programs, either in textual source form or in precompiled binary form.
(Precompiled binaries are output by luac, the Lua compiler.) lua can be used as a batch interpreter and also interactively.
The given options (see below) are executed and then the Lua program in file script is loaded and executed. The given args are available to
script as strings in a global table named arg. If these arguments contain spaces or other characters special to the shell, then they
should be quoted (but note that the quotes will be removed by the shell). The arguments in arg start at 0, which contains the string
'script'. The index of the last argument is stored in arg.n. The arguments given in the command line before script, including the name of
the interpreter, are available in negative indices in arg.
At the very start, before even handling the command line, lua executes the contents of the environment variable LUA_INIT, if it is defined.
If the value of LUA_INIT is of the form '@filename', then filename is executed. Otherwise, the string is assumed to be a Lua statement and
is executed.
Options start with '-' and are described below. You can use '--' to signal the end of options.
If no arguments are given, then -v -i is assumed when the standard input is a terminal; otherwise, - is assumed.
In interactive mode, lua prompts the user, reads lines from the standard input, and executes them as they are read. If a line does not
contain a complete statement, then a secondary prompt is displayed and lines are read until a complete statement is formed or a syntax
error is found. So, one way to interrupt the reading of an incomplete statement is to force a syntax error: adding a ';' in the middle of
a statement is a sure way of forcing a syntax error (except inside multiline strings and comments; these must be closed explicitly). If a
line starts with '=', then lua displays the values of all the expressions in the remainder of the line. The expressions must be separated
by commas. The primary prompt is the value of the global variable _PROMPT, if this value is a string; otherwise, the default prompt is
used. Similarly, the secondary prompt is the value of the global variable _PROMPT2. So, to change the prompts, set the corresponding
variable to a string of your choice. You can do that after calling the interpreter or on the command line (but in this case you have to be
careful with quotes if the prompt string contains a space; otherwise you may confuse the shell.) The default prompts are "> " and ">> ".
OPTIONS
- load and execute the standard input as a file, that is, not interactively, even when the standard input is a terminal.
-e stat
execute statement stat. You need to quote stat if it contains spaces, quotes, or other characters special to the shell.
-i enter interactive mode after script is executed.
-l name
call require('name') before executing script. Typically used to load libraries.
-v show version information.
SEE ALSO luac(1)
http://www.lua.org/
DIAGNOSTICS
Error messages should be self explanatory.
AUTHORS
R. Ierusalimschy, L. H. de Figueiredo, and W. Celes
$Date: 2006/01/06 16:03:34 $ LUA(1)