09-16-2019
Someone told me not that long ago that the next big thing in computing are Regular Expressions.
Not needing such things in what I do using computers I thought, "Why, surely it is AI?"
Then I joined here and seeing you guys using them gobsmacked me. I had no idea how important BREs and EREs were until coming on here.
However a tool like that makes them easy to understand.
(Whilst in Perl mode I will learn how to use Perl's REs.)
Thanks Ravinder, great find...
This User Gave Thanks to wisecracker For This Post:
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
2. Shell Programming and Scripting
# echo "Teest string" | sed 's/e*/=>replaced=</'
=>replaced<=Teest string
So, in the above code , sed replaces at the start. does that mean sed using the pattern e* settles to zero occurence ? Why sed was not able to replace Teest string.
# echo "Teest string" | sed 's/e*//g'
Tst string
... (6 Replies)
Discussion started by: chidori
6 Replies
3. Shell Programming and Scripting
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
4. Shell Programming and Scripting
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
5. Shell Programming and Scripting
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
6. What is on Your Mind?
Our team just published this technical report on ResearchGate:
Virtualized Cyberspace - Visualizing Patterns & Anomalies for Cognitive Cyber Situational Awareness
ABSTRACT
ACKNOWLEDGMENTS
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License This... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT DEBIAN
file::find::wanted
Wanted(3pm) User Contributed Perl Documentation Wanted(3pm)
NAME
File::Find::Wanted - More obvious wrapper around File::Find
VERSION
Version 1.00
SYNOPSIS
File::Find is a great module, except that it doesn't actually find anything. Its "find()" function walks a directory tree and calls a
callback function. Unfortunately, the callback function is deceptively called "wanted", which implies that it should return a boolean
saying whether you want the file. That's not how it works.
Most of the time you call "find()", you just want to build a list of files. There are other modules that do this for you, most notably
Richard Clamp's great File::Find::Rule, but in many cases, it's overkill, and you need to learn a new syntax.
With the "find_wanted" function, you supply a callback sub and a list of starting directories, but the sub actually should return a boolean
saying whether you want the file in your list or not.
To get a list of all files ending in .jpg:
my @files = find_wanted( sub { -f && /.jpg$/ }, $dir );
For a list of all directories that are not CVS or .svn:
my @files = find_wanted( sub { -d && !/^(CVS|.svn)$/ }, $dir ) );
It's easy, direct, and simple.
WHY DO THIS
?
The cynical may say "that's just the same as doing this":
my @files;
find( sub { push @files, $File::Find::name if -f && /.jpg$/ }, $dir );
Sure it is, but File::Find::Wanted makes it more obvious, and saves a line of code. That's worth it to me. I'd like it if find_wanted()
made its way into the File::Find distro, but for now, this will do.
FUNCTIONS
find_wanted( &wanted, @directories )
Descends through @directories, calling the wanted function as it finds each file. The function returns a list of all the files and
directories for which the wanted function returned a true value.
This is just a wrapper around "File::Find::find()". See File::Find for details on how to modify its behavior.
COPYRIGHT & LICENSE
Copyright 2005-2012 Andy Lester.
This program is free software; you can redistribute it and/or modify it under the terms of the Artistic License v2.0.
perl v5.14.2 2012-06-08 Wanted(3pm)