Sponsored Content
Top Forums Shell Programming and Scripting Question about REGEX Patterns and Case Sensitivity? Post 302716407 by mrm5102 on Tuesday 16th of October 2012 10:02:54 AM
Old 10-16-2012
Hey Spacebar, thanks for the reply...

Sorry, I probably should have mentioned what I'm trying to do. Duhh, sorry about that...
Basically, I'm trying to "verify" some user input in the script. The user should enter some text. Then I check that text in the script to
make sure that the user's input "BEGINS" with an ALL lowercase string. I'll give the "[:lower:]" Character Class a try.
Maybe that will work...



Hey Don Cragun, thanks for your reply.

Is this the info your talking about, for what character encoding I'm using..? Also, the second one below I ran the "file" command
on one of my 'test' scripts to see what its encoding was...
Code:
# echo $LANG
en_US.utf8

# file -bi test_bashScript
text/x-shellscript; charset=us-ascii

Also, your saying the "[A-z]" range should work? I thought that everytime I tried using that, it would always, no matter the input,
would return "true" or "False", I forget exactly what the return value was. But I do remember that it always had the same
result everytime...



Basically, I just want to make sure that the entire "first" string that the user enters is in all lowercase...

And I'm just VERY confused why if the input string is "HELLO" (all uppercase) and the following test (below) is returning TRUE...??
Code:
#!/bin/bash

MY_VAR="HELLO"

### This pattern SHOULD match a string that begins with ONLY "lowercase letters", zero or more times...
PATTERN_1="^[a-z]*"

### This prints "TRUE"
if [[ $MY_VAR =~ $PATTERN_1 ]]
 then
    echo "TRUE"
else
    echo "FALSE"
fi

Any idea why I'm getting "TRUE" when the input is ALL uppercase letters..?


Thanks Again,
Matt
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Case sensitivity

Is there any way of stopping UNIX from being case sensitive? (2 Replies)
Discussion started by: Taveirne
2 Replies

2. UNIX for Dummies Questions & Answers

anchoring regex using case and ksh

Outside this process I built a file containing snmp response filtering for hostname, model type and ios version. I want to get a count across the network of those devices running 11.x code, 12.0 mainline, 12.0 T train and above, 12.1 and above and OS levels. This works ok .. but its cheap... (2 Replies)
Discussion started by: popeye
2 Replies

3. Shell Programming and Scripting

bash regex =~ case insensetive, possible?

It can get very annoying that bash regex =~ is case-sensetive, is there a way to set it to be case-insensetive? if ]; then echo match else echo no match fi (8 Replies)
Discussion started by: TehOne
8 Replies

4. Shell Programming and Scripting

[BASH] recognise new line regex in case statement

Hi, I'm trying to write a routine to parse a file that contains data that will be read into arrays. The file is composed of labels to identify data types and arbitrary lines of data with the usual remarks and empty new lines as is common with config files. The initial pass is built as so:... (3 Replies)
Discussion started by: ASGR
3 Replies

5. Shell Programming and Scripting

Capture values using multiple regex patterns

I have to read the file, in each line of file i need to get 2 values using more than one search pattern. ex: <0112 02:12:20 def > /some string/some string||some string||124 i donot have same delimiter in the line, I have to read '0112 02:12:20' which is timestamp, and last field '124' which is... (4 Replies)
Discussion started by: adars1
4 Replies

6. UNIX for Dummies Questions & Answers

Is there a way to ignore CAPS or case sensitivity?

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

7. Shell Programming and Scripting

Search by patterns case

42 network read failed sv1 sv23 sv4 sv11 sv23 sv5 sv 7 48 client hostname could not be found sv21 sv78 sv19 sv22 sv111 sv203 sv5 sv 33 49 client did not start sv1 sv21 54 timed out connecting to client sv2 sv4 sv12 above is my file , I'd like to use a script to list all name... (5 Replies)
Discussion started by: Sara_84
5 Replies

8. Shell Programming and Scripting

Regex patterns

can someone please confirm for me if i'm right: the pattern: ORA-0*(600?|7445|4) can someone give me an idea of all the entries the pattern above will grab from a database log file? is it looking for the following strings?: ORA-0600 ORA-7445 4) (2 Replies)
Discussion started by: SkySmart
2 Replies

9. Shell Programming and Scripting

Convert text between exact matching patterns to Title case

Hi Folks, I have a large text file with multiple similar patterns on each line like: blank">PATTERN1 some word PATTERN2 title=">PATTERN1 some word PATTERN2 blank">PATTERN1 another word PATTERN2 title=">PATTERN1 another word PATTERN2 blank">PATTERN1 one more time PATTERN2 title=">PATTERN1... (10 Replies)
Discussion started by: martinsmith
10 Replies

10. Programming

Regarding a GREAT site for understanding and Visualizing regex patterns.

Hello All, While googling on regex I came across a site named Regulex Regulex:JavaScript Regular Expression Visualizer I have written a simple regex ^(a|b|c)(*)@(.*) and could see its visualization; one could export it too, following is the screen shot. ... (3 Replies)
Discussion started by: RavinderSingh13
3 Replies
base32::hex(n)							  Base32 encoding						    base32::hex(n)

__________________________________________________________________________________________________________________________________________________

NAME
base32::hex - base32 extended hex encoding SYNOPSIS
package require Tcl 8.4 package require base32::core ?0.1? package require base32::hex ?0.1? ::base32::hex::encode string ::base32::hex::decode estring _________________________________________________________________ DESCRIPTION
This package provides commands for encoding and decoding of strings into and out of the extended hex base32 encoding as specified in the RFC 3548bis draft. API
::base32::hex::encode string This command encodes the given string in extended hex base32 and returns the encoded string as its result. The result may be padded with the character = to signal a partial encoding at the end of the input string. ::base32::hex::decode estring This commands takes the estring and decodes it under the assumption that it is a valid extended hex base32 encoded string. The result of the decoding is returned as the result of the command. Note that while the encoder will generate only uppercase characters this decoder accepts input in lowercase as well. The command will always throw an error whenever encountering conditions which signal some type of bogus input, namely if [1] the input contains characters which are not valid output of a extended hex base32 encoder, [2] the length of the input is not a multiple of eight, [3] padding appears not at the end of input, but in the middle, [4] the padding has not of length six, four, three, or one characters, CODE MAP
The code map used to convert 5-bit sequences is shown below, with the numeric id of the bit sequences to the left and the character used to encode it to the right. The important feature of the extended hex mapping is that the first 16 codes map to the digits and hex characters. 0 0 9 9 18 I 27 R 1 1 10 A 19 J 28 S 2 2 11 B 20 K 29 T 3 3 12 C 21 L 30 U 4 4 13 D 22 M 31 V 5 5 14 E 23 N 6 6 15 F 24 O 7 7 16 G 25 P 8 8 17 H 26 Q BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category base32 of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
base32, hex, rfc3548 COPYRIGHT
Copyright (c) Public domain base32 0.1 base32::hex(n)
All times are GMT -4. The time now is 02:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy