10-20-2014
Quote:
Originally Posted by
kraljic
What is the role of * in this ?
It is a modifier, meaning "zero or more of the previous thing". ? means "zero or one of the previous thing", and + means "one or more ..." etc.
Quote:
And what is that dot (in red) doing outside the double quotes ? !!
It ends the sentence in my previous post. It's not actually part of the expression.
This User Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to figure out how to build a small shell script that will find old .shtml files in every /tgp/ directory on the server and delete them if they are older than 10 days...
The structure of the paths are like this:
/home/domains/www.domain2.com/tgp/
/home/domains/www.domain3.com/tgp/... (1 Reply)
Discussion started by: Neko
1 Replies
2. UNIX for Dummies Questions & Answers
what will the cmd below do?
ls *.3
1 members mentions that to seek all permutations and combinations of the mp3 extension ill have to use curly braces, {} and not, .
what then will do? (13 Replies)
Discussion started by: abhi
13 Replies
3. Shell Programming and Scripting
How can
grep G.*schema
give me the result: ${Gacntg_dt}""'"'
doesn't G.*schema say give me an unlimited number of characters between G and schema?
:confused: (3 Replies)
Discussion started by: danmauer
3 Replies
4. Shell Programming and Scripting
i have got heaps of files (.pdf, .txt and .doc) files in one folder, i am making a program in PERL that helps me find the files i want easier using shell wildcard,
something like this!!
print "Enter a pattern: (must be in )";
$input = <STDIN>;
if (The input is in and valid wildcard... (3 Replies)
Discussion started by: bshell_1214
3 Replies
5. Shell Programming and Scripting
Hi,
I'm on a Linux machine with a bash shell. I have some apache logs from where I want to extract the lines that match this pattern :
"GET /dir1/dir2/dir3/bt_sx.gif HTTP/1.1"
but where "/dir1/dir2/dir3/bt_sx" may vary , so I would like to grep something like
cat apache.log | grep "\"GET... (2 Replies)
Discussion started by: black_fender
2 Replies
6. Shell Programming and Scripting
How can i grep for a pattern with wildcard using grep?
I want to identify all the lines that start with SAM and end in .PIPE
IN.TXT
SAM_HEADER.PIPE
SAM_DETAIL.PIPE
SAM_INVOICE.PIPE
Can i do something like
grep SAM*.PIPE IN.TXT (2 Replies)
Discussion started by: venky338
2 Replies
7. OS X (Apple)
CD_numb is AM017
this code:
set the_Firstcom_CD to (do shell script "ls -d '/volumes/audioNAS/Firstcom/Access Music/' ") & CD_numb
gives me this:
"/volumes/audioNAS/Firstcom/Access Music/AM017"
the item I am looking for is AM017Q.
I can get the "*" syntax right so it never finder... (7 Replies)
Discussion started by: sbrady
7 Replies
8. Shell Programming and Scripting
Hello All,
I hope this is the right area. If not, Kindly let me know and I will report in the appropriate spot.
I am needing to find a search pattern that will make the * act as Wildcard in the search pattern instead of being literal.
The example I am using is bzgrep "to=<*@domain.com>"... (5 Replies)
Discussion started by: mancountry
5 Replies
9. Shell Programming and Scripting
hi anyone
how can use grep with wildcard. for example grep "sample?txt" filename doesn't show sample1txt or grep "sample*txt" filename doesn't show sample123.txt that there is in filename.
many thanks
samad (12 Replies)
Discussion started by: abdossamad2003
12 Replies
10. Shell Programming and Scripting
I wish to check if my file has a line that does not start with '#' and has
1. Listen and 2. 443
echo "Listen 443" > test.out
grep 'Listen *443' test.out | grep -v '#'
Listen 443
The above worked fine but when the entry changes to the below the grep fails... (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT CENTOS
perl::critic::policy::regularexpressions::requireextendedformatt
Perl::Critic::Policy::RegularExpressions::RequireExtendeUsermContributed PerPerl::Critic::Policy::RegularExpressions::RequireExtendedFormatting(3)
NAME
Perl::Critic::Policy::RegularExpressions::RequireExtendedFormatting - Always use the "/x" modifier with regular expressions.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Extended regular expression formatting allows you mix whitespace and comments into the pattern, thus making them much more readable.
# Match a single-quoted string efficiently...
m{'[^\']*(?:\.[^\']*)*'}; #Huh?
# Same thing with extended format...
m{
' # an opening single quote
[^\'] # any non-special chars (i.e. not backslash or single quote)
(?: # then all of...
\ . # any explicitly backslashed char
[^\']* # followed by an non-special chars
)* # ...repeated zero or more times
' # a closing single quote
}x;
CONFIGURATION
You might find that putting a "/x" on short regular expressions to be excessive. An exception can be made for them by setting
"minimum_regex_length_to_complain_about" to the minimum match length you'll allow without a "/x". The length only counts the regular
expression, not the braces or operators.
[RegularExpressions::RequireExtendedFormatting]
minimum_regex_length_to_complain_about = 5
$num =~ m<(d+)>; # ok, only 5 characters
$num =~ m<d.(d+)>; # not ok, 9 characters
This option defaults to 0.
Because using "/x" on a regex which has whitespace in it can make it harder to read (you have to escape all that innocent whitespace), by
default, you can have a regular expression that only contains whitespace and word characters without the modifier. If you want to restrict
this, turn on the "strict" option.
[RegularExpressions::RequireExtendedFormatting]
strict = 1
$string =~ m/Basset hounds got long ears/; # no longer ok
This option defaults to false.
NOTES
For common regular expressions like e-mail addresses, phone numbers, dates, etc., have a look at the Regexp::Common module. Also, be
cautions about slapping modifier flags onto existing regular expressions, as they can drastically alter their meaning. See
<http://www.perlmonks.org/?node_id=484238> for an interesting discussion on the effects of blindly modifying regular expression flags.
TO DO
Add an exemption for regular expressions that contain "Q" at the front and don't use "E" until the very end, if at all.
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-Perl::Critic::Policy::RegularExpressions::RequireExtendedFormatting(3)