Sponsored Content
Full Discussion: Validating user input
Top Forums UNIX for Dummies Questions & Answers Validating user input Post 302373924 by Scrutinizer on Monday 23rd of November 2009 12:49:23 AM
Old 11-23-2009
In bash/ksh you could use e.g.
Code:
if [ "$NAME" = "" ] || [ "${NAME//[!0-9]}" != "" ];

But I would just use a case statement, which is universal and easier to understand:
Code:
case $NAME in 
  ""|*[0-9]*) 
        echo "You have not entered a name."
        echo "Please try again."
        ;;
  *)
        echo "Your name is $NAME."
        break
        ;;
esac

 

10 More Discussions You Might Find Interesting

1. Programming

validating input

how do i validate y script so that it only accepts values between 1 and 3 and against any character input, cause at the moment i can only validate against numbers outside 1 and 3 but not characters cheers (4 Replies)
Discussion started by: ruffenator
4 Replies

2. Shell Programming and Scripting

validating input using regular expressions

I am trying to validate input from the user in a script. I thought is was easy to do using regular expressions but I can't figure out how to use REs in a conditional. I have tried using grep from a temp file, sed from a temp file, sed from command line, comparison in an if condition and I cannot... (1 Reply)
Discussion started by: nrodolfich
1 Replies

3. Shell Programming and Scripting

Validating the input date format

I have one script.for that the inputs are fromdate(dd/mon/yyyy) and todate(dd/mon/yyyy). How i can validate the input format?for eg.27/08/2008 is not valid.27/aug/2008 or 27/Aug/2008 are valid. and the todate is optional.so if the todate is not present in the input then i need to assign the... (6 Replies)
Discussion started by: Sharmila_P
6 Replies

4. Shell Programming and Scripting

Validating user input is not blank

Trying to create a script in BASH that would ask the user to enter another user name making sure the input is not blank before they hit enter then to check the home directory of that user does exist, I have the check folder sorted it's just the loop to make sure the user has entered chars (5 Replies)
Discussion started by: MBN
5 Replies

5. Shell Programming and Scripting

validating a input file for numeric and character

i have a input file like this 001|rahim|bajaj|20090102 while reading the file i need to check whether the first column is a number second column is a name is there any methodology to check for the same thanks in advance (2 Replies)
Discussion started by: trichyselva
2 Replies

6. UNIX for Dummies Questions & Answers

Validating input based on fixed number of fields

Yes, i did... let me state my problem in more detail Inputs: I have one input CSV file And, i have stored no. of comma each line should in a variable. e.g. $ cat cmt.csv this, is a ,comma ,count test1 ,,this, is a ,comma ,count test2 this, is a ,comma ,count test3... (6 Replies)
Discussion started by: Dipali
6 Replies

7. Shell Programming and Scripting

Validating Input parameters

Hi All, I have tried to use ckdate (sun) command in script. It checks the input parameter which should be in 'YYYYMMDD format. date=$( echo $1 | ckdate -f "%Y%m%d") | true if ] then print " success" else print "no success" fi But in whatever format i pass the parameter,... (3 Replies)
Discussion started by: Amit.Sagpariya
3 Replies

8. Shell Programming and Scripting

validating user entered date

I need the date validation. I searched in the google but i didn't find my requirements. requirements: 1) user has to enter the date in YYYY/MM/DD format 2) MM validations 3) DD validations. and if the month is april it should allow 30 days only and for May month it should allow 31 days like... (1 Reply)
Discussion started by: KiranKumarKarre
1 Replies

9. Shell Programming and Scripting

Validating uppercase/lowercase of user input with perl compared to unix folders

Hi, I need to copy files from a source directory to a destination directory in unix. I'm using the file::copy for the actual copy. The problem is that the source and dest directories are supplied by different users, who might type the name of the directories in various combinations of lower... (6 Replies)
Discussion started by: Furou
6 Replies

10. Shell Programming and Scripting

How to get the user input recursively until the user provides valid input

Hi, echo "Enter file name of input file list along with absolute path : " read inputFileList if then for string in `cat inputFileList` do echo $string done else echo " file does not exist" fi From the above code, if the user enters a invalid file... (1 Reply)
Discussion started by: i.srini89
1 Replies
GROG(1) 						      General Commands Manual							   GROG(1)

NAME
grog - guess options for groff command SYNOPSIS
grog [-C] [groff-option ...] [--] [filespec ...] grog -h | --help grog -v | --version DESCRIPTION
grog reads the input (file names or standard input) and guesses which of the groff(1) options are needed to perform the input with the groff program. The corresponding groff command is output. OPTIONS
The only grog options recognized are -C (which is also passed on) to enable compatibility mode; -v and --version print information on the version number; and -h and --help print usage information. -v, --version, -h, and --help stop the program directly without printing a groff command to standard output. All other specified short options (words starting with one minus character -) are interpreted as groff options or option clusters with or without argument. No space is allowed between options and their argument. Except from the -marg options, all options will be passed on, i.e. they are included unchanged in the command for the output without effecting the work of grog. A filespec argument can either be the name of an existing file or a single minus - to mean standard input. If no filespec is specified standard input is read automatically. DETAILS
grog reads all filespec parameters as a whole. It tries to guess which of the following groff options are required for running the input under groff: -e, -man, -me, -mm, -mom, -ms, -mdoc, -mdoc-old, -p, -R, -g, -G, -s, and -t. The guessed groff command including those options and the found filespec parameters is put on the standard output. It is possible to specify arbitrary groff options on the command line. These are passed on the output without change, except for the -marg options. The groff program has trouble when the wrong -marg option or several of these options are specified. In these cases, grog will print an error message and exit with an error code. It is better to specify no -marg option. Because such an option is only accepted and passed when grog does not find any of these options or the same option is found. If several different -marg options are found by grog an error message is produced and the program is terminated with an error code. But the output is written with the wrong options nevertheless. Remember that it is not necessary to determine a macro package. A roff file can also be written in the groff language without any macro package. grog will produce an output without an -marg option. As groff also works with pure text files without any roff requests, grog cannot be used to identify a file to be a roff file. The groffer(1) program heavily depends on a working grog. The grog source contains two files written in different programming languages: grog.pl is the Perl version, while grog.sh is a shell script using BR awk (1). During the run of make(1), it is determined whether the system contains a suitable version of perl(1). If so, grog.pl is transformed into grog; otherwise grog.sh is used instead. EXAMPLES
o Calling grog meintro.me results in groff -me meintro.me So grog recognized that the file meintro.me is written with the -me macro package. o On the other hand, grog pic.ms outputs groff -pte -ms pic.ms Besides determining the macro package -ms, grog recognized that the file pic.ms additionally needs -pte, the combination of -p for pic, -t for tbl, and -e for eqn. o If both files are combined by the command grog meintro.me pic.ms an error message is sent to standard error because groff cannot work with two different macro packages: grog: error: there are several macro packages: -me -ms Additionally the corresponding output with the wrong options is printed to standard output: groff -pte -me -ms meintro.me pic.ms But the program is terminated with an error code. o The call of grog -ksS -Tdvi grnexmpl.g contains several groff options that are just passed on the output without any interface to grog. These are the option cluster -ksS consisting of -k, -s, and -S; and the option -T with argument dvi. The output is groff -ksS -Tdvi grnexmpl.g so no additional option was added by grog. As no option -marg was found by grog this file does not use a macro package. o grog can also handle files using the chem language. The example grog chAh_brackets.chem outputs chem chAh_brackets.chem | groff -pe So chem is run first and groff is appended. The option -p for pic is implied automatically by chem. Additionally, the file uses eqn with -e. SEE ALSO
groff(1), troff(1), tbl(1), pic(1), eqn(1), refer(1), grn(1), grap(1), soelim(1), groff_me(7), groff_ms(7), groff_mm(7), groff_mom(7), groff_man(7), groffer(1) COPYING
Copyright (C) 1989-2000, 2001, 2002, 2003, 2006, 2007, 2009, 2010 Free Software Foundation, Inc. Written by James Clark. Maintained by Werner Lemberg <wl@gnu.org>. Rewritten and put under GPL by Bernd Warken. This file is part of grog, which is part of groff, a free software project. You can redistribute it and/or modify it under the terms of the GNU General Public License (GPL) as published by the Free Software Foundation, either version 2, or (at your option) any later version. You should have received a copy of the GNU General Public License along with groff, see the files COPYING and LICENSE in the top directory of the groff source package. Or read the man page gpl(1). You can also write to the Free Software Foundation, 51 Franklin St - Fifth Floor, Boston, MA 02110-1301, USA. Groff Version 1.21 31 December 2010 GROG(1)
All times are GMT -4. The time now is 01:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy