09-15-2009
typeset -u var # convert to uppercase no matter what the input is
# checks for all possible input combos
echo $var | sed 's/^YES$/valid/
s/^NO$/valid
s/^Y$/valid
s/$N$/valid'
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
New to this Unix dot com.
I would like to know how i can ignore the case in filename which is getting as user directoty to shell script.
For Ex:
Source (/aa/bb/patch/)
Directory may contains more than 1 files as like
1. aa.csv or Aa.csv or AA.csv or aa.CSV
2. bb.csv
3. ... (3 Replies)
Discussion started by: AAH
3 Replies
2. Shell Programming and Scripting
In a Case switch, how to ignore case sensitive in the test:
e.g.
case "$field" in
"TEST) action1;;
*) action2;;
esac
How to go in action1 in case of $field = TEST , or Test , or test or .... without enumerating all possibilities...
Thanks,... (1 Reply)
Discussion started by: annelisa
1 Replies
3. Shell Programming and Scripting
Hello, I am new to this forums. I need help with shell, and ksh in particular. I have a case statement that does something if -k. So it looks like:
case $arg in
-k) PUT=y, SEND=1
Thats all good and dandy. But now I want to change it where whether or not the user puts -k or not, it will do... (2 Replies)
Discussion started by: cpunisher
2 Replies
4. Programming
How do I ignore the case in an if condition..?
EDIT: I put this in the wrong board...this is a linux script.
if
then
echo "Same name."
else
echo "Different name."
fi (1 Reply)
Discussion started by: Bandit390
1 Replies
5. Shell Programming and Scripting
hi, i will like to know whether awk command can ignore case?
i written a script that will take in user input and search for data on the 1st field from a text file.
echo -n "Title:"
read title
awk -F":" '$1~/'"$title"'/{print $0}' Filename
read ans
return
... (5 Replies)
Discussion started by: Cheranime
5 Replies
6. Shell Programming and Scripting
Folks - I found this code on the forums to extract a paragraph for a matching pattern but I don't know how to make it ignore case.
grep "-ip" is not an option for me as I am on SUSE LINUX.
Thanks for ur help.
I run this script as below:
grep_para.ksh sqlstate < logfile
"The end result... (2 Replies)
Discussion started by: beowulfkid
2 Replies
7. UNIX for Dummies Questions & Answers
If I'm using a program that is expecting certain filenames and directories to be all CAPS, isn't there a way to ignore this in linux/cshell scripting? I.e., similiar to ignoring spaces with " (i.e., directory is directory 1, can ignore by typing "directory 1".) ?? (2 Replies)
Discussion started by: rebazon
2 Replies
8. Shell Programming and Scripting
Hi ,
I have the file where i have to search for the pattern. The pattern may be lower case or upper case or camel case. Basically I want to ignore while searching the pattern in awk.
awk '/error|warning/exception/' filename
Please help me (3 Replies)
Discussion started by: arukuku
3 Replies
9. Shell Programming and Scripting
I have a bi-lingual database of a large number of dictionaries. It so happens that in some a given string is in upper case and in others it is in lower case. An example will illustrate the issue.
toll Tax=पथ-कर
Toll tax=राहदारी कर
toll tax=टोल
I want to treat all three instances of toll tax... (3 Replies)
Discussion started by: gimley
3 Replies
10. UNIX for Beginners Questions & Answers
Hi,
How can i ignore case between 2 files in unix using COMM command.
2 input files are:
-bash-4.1$ more x2.txt
HELLO
hi
HI
raj
-bash-4.1$ more x3.txt
hello
hi
raj
COMM command:
-bash-4.1$ comm x2.txt x3.txt
hello
HELLO
hi (3 Replies)
Discussion started by: raju2016
3 Replies
LEARN ABOUT SUSE
flipdiff
FLIPDIFF(1) Man pages FLIPDIFF(1)
NAME
flipdiff - exchange the order of two incremental patches
SYNOPSIS
flipdiff [[-p n] | [--strip-match=n]] [[-U n] | [--unified=n]] [[-d PAT] | [--drop-context=PAT]] [[-q] | [--quiet]] [[-z] | [--decompress]]
[[-b] | [--ignore-space-change]] [[-B] | [--ignore-blank-lines]] [[-i] | [--ignore-case]] [[-w] | [--ignore-all-space]]
[--in-place] diff1 diff2
flipdiff {[--help] | [--version]}
DESCRIPTION
flipdiff exchanges the order of two patch files that apply one after the other. The patches must be "clean": the context lines must match
and there should be no mis-matched offsets.
The swapped patches are sent to standard output, with a marker line ("=== 8< === cut here === 8< ===") between them, unless the --in-place
option is passed. In that case, the output is written back to the original input files.
OPTIONS
-p n, --strip-match=n
When comparing filenames, ignore the first n pathname components from both patches. (This is similar to the -p option to GNU patch(1).)
-q, --quiet
Quieter output. Don't emit rationale lines at the beginning of each patch.
-U n, --unified=n
Attempt to display n lines of context (requires at least n lines of context in both input files). (This is similar to the -U option to
GNU diff(1).)
-d pattern, --drop-context=PATTERN
Don't display any context on files that match the shell wildcard pattern. This option can be given multiple times.
Note that the interpretation of the shell wildcard pattern does not count slash characters or periods as special (in other words, no
flags are given to fnmatch). This is so that "*/basename"-type patterns can be given without limiting the number of pathname
components.
-i, --ignore-case
Consider upper- and lower-case to be the same.
-w, --ignore-all-space
Ignore whitespace changes in patches.
-b, --ignore-space-change
Ignore changes in the amount of whitespace.
-B, --ignore-blank-lines
Ignore changes whose lines are all blank.
-z, --decompress
Decompress files with extensions .gz and .bz2.
--in-place
Write output to the original input files.
--help
Display a short usage message.
--version
Display the version number of flipdiff.
LIMITATIONS
This is only been very lightly tested, and may not even work. Using --in-place is not recommended at the moment.
There are some cases in which it is not possible to meaningfully flip patches without understanding the semantics of the content. This
program only uses complete lines that appear at some stage during the application of the two patches, and never composes a line from parts.
Because of this, it is generally a good idea to read through the output to check that it makes sense.
AUTHOR
Tim Waugh <twaugh@redhat.com>
Package maintainer
patchutils 23 January 2009 FLIPDIFF(1)