bash regex =~ case insensetive, possible? Post: 302318451

10 More Discussions You Might Find Interesting

1. 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. Shell Programming and Scripting

How to specify 'not case sensitive' in regex (nawk, sed, patern expencions)?

Is it possible to make the search in regular exprecion or in matching parts of sed, nawk and others to IGNORE the case of the search string? I mean, like if used 'grep' with -i option: > grep -i "abc" file I would like to be able to do the same, say, by nawk: > nawk '/abc/ {print $0}'...

3. 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:...

4. Shell Programming and Scripting

Bash regex

Hello everybody, I'm clearly not an expert in bash scripting as I've written maybe less than 10 scripts in my life. I'm trying to strip an xml string removing every tag in it. I'm using bash substitution to do so, but apparently I missed something about what is a regex for bash ... As an...

5. Shell Programming and Scripting

[BASH] Allow name with spaces (regex)

Hey all, I have a very simple regular expression that I use when I want to allow only letters with spaces. (I know this regex has a lot of shortcomings, but I'm still trying to learn them) isAlpha='^*$'However, when I bring this over to BASH it doesn't allow me to enter spaces. I use the...

6. Shell Programming and Scripting

Bash regex help

I've been using the following regex below in a bash script on RHEL 5.5 using version GNU bash, version 3.2.25(1)-release I've tried using the script on RHEL 6.3 which uses GNU bash, version 4.1.2(1)-release I assume there's been alot of changes to bash since that's quite a jump in revisions....

7. Shell Programming and Scripting

Question about REGEX Patterns and Case Sensitivity?

Hello All, I'm in the middle of a script and I'm doing some checks with REGEX (i.e. using the '"shopt -s nocasematch" that at least the first one should print "FALSE" but it prints "TRUE"..? For Example: #!/bin/bash MY_VAR="HELLO" ### This prints "TRUE" PATTERN_1="^*" if ] then...

8. UNIX for Dummies Questions & Answers

Need help with Regex for bash

Hi, I am trying to match this word: hexagon-bx.mydomain.com with regex. I have tried this: "\.*]*$" So far I have not been successful. I also need to make sure that the regex will match words that just have lowercase letters and numbers in them, such as camera01. How can I create such an...

9. UNIX for Dummies Questions & Answers

Regex for (a|b) in bash

I am trying to find files using the following by using simple bash script: if -2014 ]]; then echo "yes";fi What I need to find are any files with date 08-**-2014 so August 2014 any files. I can use if -2014 ]]; then echo "yes";fi That works fine. How do I get files beginning with 08...

10. Shell Programming and Scripting

Using RegEx with variable within bash if [[ ]]

I stumbled upon a problem, which I simplified to this: There is a list of numbers, stored in variable $LIST, lets use `seq 5 25` for demonstration. There is a number that should be compared against this list. For demonstration I use user input - read VALUE I am trying to compare RegEx...

LEARN ABOUT OPENSOLARIS

echo

echo(1B)					     SunOS/BSD Compatibility Package Commands						  echo(1B)

NAME

       echo - echo arguments to standard output

SYNOPSIS

       /usr/ucb/echo [-n] [argument]

DESCRIPTION

       echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.

       echo  is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
       ronment variables.

       For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:

	   o	  echo your current-working-directory's full pathname

	   o	  pipe the output through tr to translate the path's embedded slash-characters into space-characters

	   o	  pipe that output through wc -w for a count of the names in your path.

		    example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"

       See tr(1) and wc(1) for their functionality.

       The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be  invoked	if
       the  user  calls  echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
       characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the  black-slashed  escape  characters,	and  ksh's
       echo() also understands a as the audible bell character; however, these commands do not have an -n option.

OPTIONS

       -n    Do not add the NEWLINE to the output.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWscpu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)

NOTES

       The -n option is a transition aid for BSD applications, and may not be supported in future  releases.

SunOS 5.11							    3 Aug 1994								  echo(1B)