Sponsored Content
Top Forums Shell Programming and Scripting Understanding regex behaviour when using quantifiers Post 302749725 by chidori on Saturday 29th of December 2012 05:36:38 AM
Old 12-29-2012
:)

Quote:
Originally Posted by jim mcnamara
There even more interesting aspects to regular expressions.
Consider reading the 'owl' book: Mastering Regular Expressions 3rd Ed by J. Friedl
Thanks, I got one already. Guess its good time to start reading that Smilie

Thanks to all who for a brief explanation on this Smilie
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Converting perl regex to sed regex

I am having trouble parsing rpm filenames in a shell script.. I found a snippet of perl code that will perform the task but I really don't have time to rewrite the entire script in perl. I cannot for the life of me convert this code into something sed-friendly: if ($rpm =~ /(*)-(*)-(*)\.(.*)/)... (1 Reply)
Discussion started by: suntzu
1 Replies

2. Shell Programming and Scripting

find: "weird" regex behaviour

I have these two files in current dir: oos.txt oos_(copy).txt I execute this find command:find . -regex './oos*.txt'And this outputs only the first file (oos.txt)! :confused: Only if I add another asterisk to the find find . -regex './oos*.*txt' do I also get the second file... (7 Replies)
Discussion started by: courteous
7 Replies

3. Shell Programming and Scripting

Understanding a regex

Hi, Please help me to understand the bold segments in the below regex. Both are of same type whose meaning I am looking for. find . \( -iregex './\{6,10\}./src' \) -type d -maxdepth 2 Output: ./20111210.0/src In continuation to above: sed -e 's|./\(*.\{1,3\}\).*|\1|g' Output: ... (4 Replies)
Discussion started by: vibhor_agarwali
4 Replies

4. Shell Programming and Scripting

help understanding regex with grep & sed

I have the following line of code that works wonders. I just don't completely understand it as I am just starting to learn regex. Can you help me understand exactly what is happening here? find . -type f | grep -v '^\.$' | sed 's!\.\/!!' (4 Replies)
Discussion started by: trogdortheburni
4 Replies

5. Shell Programming and Scripting

Need Quick help on Understanding sed Regex

Hi Guys, Could you please kindly explain what exactly the below SED command will do ? I am quite confused and i assumed that, sed 's/*$/ /' 1. It will remove tab and extra spaces .. with single space. The issue is if it is removing tab then it should be Î right .. please assist.... (3 Replies)
Discussion started by: Nandy
3 Replies

6. Shell Programming and Scripting

Perl, RegEx - Help me to understand the regex!

I am not a big expert in regex and have just little understanding of that language. Could you help me to understand the regular Perl expression: ^(?!if\b|else\b|while\b|)(?:+?\s+){1,6}(+\s*)\(*\) *?(?:^*;?+){0,10}\{ ------ This is regex to select functions from a C/C++ source and defined in... (2 Replies)
Discussion started by: alex_5161
2 Replies

7. Shell Programming and Scripting

Need help understanding this Regex.

Hi everyone, This regex looks simple and yet it doesn't make sense how it's manipulating the output. ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0c:49:c2:35:6v inet addr:192.16.1.1 Bcast:192.168.226.255 Mask:255.255.255.0 inet6 addr:... (2 Replies)
Discussion started by: xcod3r
2 Replies

8. Shell Programming and Scripting

Sendmail K command regex: adding exclusion/negative lookahead to regex -a@MATCH

I'm trying to get some exclusions into our sendmail regular expression for the K command. The following configuration & regex works: LOCAL_CONFIG # Kcheckaddress regex -a@MATCH +<@+?\.++?\.(us|info|to|br|bid|cn|ru) LOCAL_RULESETS SLocal_check_mail # check address against various regex... (0 Replies)
Discussion started by: RobbieTheK
0 Replies

9. UNIX for Beginners Questions & Answers

Help with understanding this regex in a Perl script parsing a 'complex' string

Hi, I need some guidance with understanding this Perl script below. I am not the author of the script and the author has not leave any documentation. I supposed it is meant to be 'easy' if you're a Perl or regex guru. I am having problem understanding what regex to use :confused: The script does... (3 Replies)
Discussion started by: newbie_01
3 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
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 11:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy