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)
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)
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)
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)
Hi All,
The means I use to ignore case, as an example is the following snippet:
It should accept any oof the following y|Y|YES|Yes|n|N|NO|No
echo "Enter Y/N to continue: "
read choice; (3 Replies)
i want to get user input like this
please tell which option to chose
1. mango 2. tango 3. rango
if user chooses mango
then it should execute a set of statements and again ask like this
what do you want to do
1.add 2.subtract 3.exit
when i choose exit it should goto my previous... (1 Reply)
i want to get user input like this
please tell which option to chose
1. mango 2. tango 3. rango
if user chooses mango
then it should execute a set of statements and again ask like this
what do you want to do
1.add 2.subtract 3.exit
when i choose exit it should goto my previous menu... (4 Replies)
Hi,
In my script it takes the input from the user. i.e. sys or system.
How can i make it case insensitive in my code.
if || ; then
echo "valid"
Any help is appreciated.
Thanks,
priya (4 Replies)
This is supposed to be a simple bank script. Whenever I try the case construct options it wont work for the deposit option after typing the amount it just goes straight back into the menu, same with withdrawal option. Option 3 which should just display the balance amount doesn't echo anything. The... (2 Replies)
I need to Write a shell script that allows some system-administration tasks to be preformed automatically from a menu-driven interface. with automated following tasks:
Copy directory tree
Delete files or directories
Output Information (this part is done )
*Copy directory tree
The “Copy... (2 Replies)
Discussion started by: femchi
2 Replies
LEARN ABOUT CENTOS
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)