Sponsored Content
Top Forums Shell Programming and Scripting Help: Regular Expression for Negate Matching String Post 302327741 by jim mcnamara on Monday 22nd of June 2009 01:24:25 PM
Old 06-22-2009
Conversely, regular expressions by themselves do one thing: find strings using pattern matching.

Again - what are you trying to do? If I remember correctly, ! negates a perl regex.
But what negation means: it still finds everything else. It returns the whole string only if the pattern match fails. Is that what you want?

In truth your question does not make a lot of sense to me.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Regular expression matching a new line

I have written a script to test some isdn links in my network and I am trying to format the output to be more readable. Each line of the output has a different number of digits as follows... Sitename , spid1 12345678901234 1234567890 1234567 , spid2 1234567890 1234567890 1234567 Sitename , ... (1 Reply)
Discussion started by: drheams
1 Replies

2. Shell Programming and Scripting

validate a string against a regular expression

Hi there i have a script which will create unix user accounts. Id like to validate the entered string so that it is specifically 8 characters or less and consists of only ! not Is there a way to validate a string against a regular expression.. i.e size=`printf "$var | wc -m` ... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

3. Programming

Regular Expression matching in PERL

I am trying to read a file and capture particular lines into different strings: LENGTH: Some Content here TEXT: Some Content Here COMMENT: Some Content Here I want to be able to get (LENGTH: .... ) into one array and so on... I'm trying to use PERL in slurp mode but for some reason... (8 Replies)
Discussion started by: Legend986
8 Replies

4. Shell Programming and Scripting

Regular expression matching in BASH (equivalent of =~ in Perl)

In Perl I can write a condition that evaluates a match expression like this: if ($foo =~ /^bar/) { do blah blah blah } How do I write this in shell? What I need to know is what operator do I use? The '=~' doesn't seem to fit. I've tried different operators, I browsed the man page for... (3 Replies)
Discussion started by: indiana_tas
3 Replies

5. Shell Programming and Scripting

Regular expression matching

Hi, I have a variable in my script that gets its value from a procstack output. It could be a number of any length, or it could just be a '1' with 0 or more white spaces around it. I would like to detect when this variable is just a 1 and not a 1234, for example. This is as far as I got: ... (3 Replies)
Discussion started by: tmf33uk
3 Replies

6. Shell Programming and Scripting

Matching single quote in a regular expression

I trying to match the begining of the following line in a perl script with a regular expression. $ENV{'ORACLE_HOME'} I tried this regluar expession: /\$ENV\{\'ORACLE_HOME\'\}/ Instead of match, I got a blank prompt > It seems to be a problem with the single quote. If I take it... (11 Replies)
Discussion started by: JC9672
11 Replies

7. Programming

Perl: How to read from a file, do regular expression and then replace the found regular expression

Hi all, How am I read a file, find the match regular expression and overwrite to the same files. open DESTINATION_FILE, "<tmptravl.dat" or die "tmptravl.dat"; open NEW_DESTINATION_FILE, ">new_tmptravl.dat" or die "new_tmptravl.dat"; while (<DESTINATION_FILE>) { # print... (1 Reply)
Discussion started by: jessy83
1 Replies

8. UNIX for Dummies Questions & Answers

delete lines matching a regular expression

I have a very large file (over 700 million lines) that has some lines that I need to delete. An example of 5 lines of the file: HS4_80:8:2303:19153:193032 153 k80:138891 HS4_80:8:2105:5544:43174 89 k88:81949 165 k88:81949 323 0 * = 323 0 ... (6 Replies)
Discussion started by: pathunkathunk
6 Replies

9. Shell Programming and Scripting

regular expression matching whole words

Hi Consider the file this is a good line when running grep '\b(good|great|excellent)\b' file5 I expect it to match the line but it doesn't... what am i doing wrong?? (ultimately this regex will be in a awk script- just using grep to test it) Thanks, Storms (5 Replies)
Discussion started by: Storms
5 Replies

10. Shell Programming and Scripting

String regular expression

Hi, temp="/usr=25,/usr/lib=12" How to get only dir names with out values. I tried like below but no use. tmp=${temp##*,} echo $tmp o/p: /usr/lib=12 expected o/p: /usr /usr/lib ---> in array (13 Replies)
Discussion started by: munna_dude
13 Replies
vgrindefs(5)                                            Standards, Environments, and Macros                                           vgrindefs(5)

NAME
vgrindefs - vgrind's language definition data base SYNOPSIS
/usr/lib/vgrindefs DESCRIPTION
vgrindefs contains all language definitions for vgrind(1). Capabilities in vgrindefs are of two types: Boolean capabilities which indicate that the language has some particular feature and string capabilities which give a regular expression or keyword list. Entries may continue onto multiple lines by giving a as the last character of a line. Lines starting with # are comments. Capabilities The following table names and describes each capability. +-------+---------+--------------------------------------------+ |Name | Type |Description | +-------+---------+--------------------------------------------+ |ab | str |Regular expression for the start of an | | | |alternate form comment | +-------+---------+--------------------------------------------+ |ae | str |Regular expression for the end of an alter- | | | |nate form comment | +-------+---------+--------------------------------------------+ |bb | str |Regular expression for the start of a block | +-------+---------+--------------------------------------------+ |be | str |Regular expression for the end of a lexical | | | |block | +-------+---------+--------------------------------------------+ |cb | str |Regular expression for the start of a com- | | | |ment | +-------+---------+--------------------------------------------+ |ce | str |Regular expression for the end of a comment | +-------+---------+--------------------------------------------+ |id | str |String giving characters other than letters | | | |and digits that may legally occur in iden- | | | |tifiers (default `_') | +-------+---------+--------------------------------------------+ |kw | str |A list of keywords separated by spaces | +-------+---------+--------------------------------------------+ |lb | str |Regular expression for the start of a char- | | | |acter constant | +-------+---------+--------------------------------------------+ |le | str |Regular expression for the end of a charac- | | | |ter constant | +-------+---------+--------------------------------------------+ |oc | bool |Present means upper and lower case are | | | |equivalent | +-------+---------+--------------------------------------------+ |pb | str |Regular expression for start of a procedure | +-------+---------+--------------------------------------------+ |pl | bool |Procedure definitions are constrained to | | | |the lexical level matched by the `px' capa- | | | |bility | +-------+---------+--------------------------------------------+ |px | str |A match for this regular expression indi- | | | |cates that procedure definitions may occur | | | |at the next lexical level. Useful for lisp- | | | |like languages in which procedure defini- | | | |tions occur as subexpressions of defuns. | +-------+---------+--------------------------------------------+ |sb | str |Regular expression for the start of a | | | |string | +-------+---------+--------------------------------------------+ |se | str |Regular expression for the end of a string | +-------+---------+--------------------------------------------+ |tc | str |Use the named entry as a continuation of | | | |this one | +-------+---------+--------------------------------------------+ |tl | bool |Present means procedures are only defined | | | |at the top lexical level | +-------+---------+--------------------------------------------+ Regular Expressions vgrindefs uses regular expressions similar to those of ex(1) and lex(1). The characters `^', `$', `:', and `' are reserved characters and must be `quoted' with a preceding if they are to be included as normal characters. The metasymbols and their meanings are: $ The end of a line ^ The beginning of a line d A delimiter (space, tab, newline, start of line) a Matches any string of symbols (like `.*' in lex) p Matches any identifier. In a procedure definition (the `pb' capability) the string that matches this symbol is used as the procedure name. () Grouping | Alternation ? Last item is optional e Preceding any string means that the string will not match an input string if the input string is preceded by an escape character (). This is typically used for languages (like C) that can include the string delimiter in a string by escaping it. Unlike other regular expressions in the system, these match words and not characters. Hence something like `(tramp|steamer)flies?' would match `tramp', `steamer', `trampflies', or `steamerflies'. Contrary to some forms of regular expressions, vgrindef alternation binds very tightly. Grouping parentheses are likely to be necessary in expressions involving alternation. Keyword List The keyword list is just a list of keywords in the language separated by spaces. If the `oc' boolean is specified, indicating that upper and lower case are equivalent, then all the keywords should be specified in lower case. EXAMPLES
Example 1: A sample program. The following entry, which describes the C language, is typical of a language entry. C|c|the C programming language: :pb=^d?*?d?pd?(a?)(d|{):bb={:be=}:cb=/*:ce=*/:sb=":se=e": :le=e':tl: :kw=asm auto break case char continue default do double else enum extern float for fortran goto if int long register return short sizeof static struct switch typedef union unsigned void while #define #else #endif #if #ifdef #ifndef #include #undef # define endif ifdef ifndef include undef defined: Note that the first field is just the language name (and any variants of it). Thus the C language could be specified to vgrind(1) as `c' or `C'. FILES
/usr/lib/vgrindefs file containing vgrind descriptions SEE ALSO
ex(1), lex(1), troff(1), vgrind(1) SunOS 5.10 10 Aug 1994 vgrindefs(5)
All times are GMT -4. The time now is 04:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy