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
email::received
Email::Received(3pm) User Contributed Perl Documentation Email::Received(3pm)
NAME
Email::Received - Parse an email Received: header
SYNOPSIS
use Email::Received;
for ($mail->header("Received")) {
my $data = parse_received($_);
return "SPAM" if rbl_lookup($data->{ip});
}
DESCRIPTION
This module is a Perl Email Project rewrite of SpamAssassin's email header parser. We did this so that the great work they did in analysing
pretty much every possible Received header format could be used in applications other than SpamAssassin itself.
The module provides one function, "parse_received", which takes a single Received line. It then produces either nothing, if the line is
unparsable, a hash reference like this:
{ reason => "gateway noise" }
if the line should be ignored for some good reason, and one like this:
{ ip => '64.12.136.4', id => '875522', by => 'xxx.com',
helo => 'imo-m01.mx.aol.com' }
if it parsed the message. Possible keys are:
ip rdns helo ident envfrom auth by id
RULE FORMAT
Where SpamAssassin used a big static subroutine full of regular expressions to parse the data, we build up a big subroutine full of regular
expressions dynamically from a set of rules. The rules are stored at the bottom of this module. The basic format for a rule looks like
this:
((var=~)?/REGEXP/)? [ACTION; ]+
The "ACTION" is either "SET variable = $value", "IGNORE "reason"?", "UNPARSABLE" or "DONE".
One control structure is provided, which is basically an "if" statement:
GIVEN (NOT)? /REGEXP/ {
ACTION+
}
EXPORT
parse_received
SEE ALSO
Mail::SpamAssassin::Message::Metadata::Received, from which the rules and some of the IP address matching constants were blatantly stolen.
Thanks, guys, for doing such a comprehensive job!
AUTHOR
simon, <simon@>
COPYRIGHT AND LICENSE
Copyright (C) 2006 by simon
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.7 or,
at your option, any later version of Perl 5 you may have available.
perl v5.10.0 2006-03-24 Email::Received(3pm)