Hi all,
I do a find | grep using  find ../ -depth -type f | xargs grep -i -n "<search Term>";
it pulls up many files, I use a regEx to get file name and path  $ResultOfGrep=~/(\w+[\.\w+[\.]?]+)(\:)/;
where $1 holds file name and $` holds path.
Sample find results are like this
/work/MergeProject/cgi-bin/log/spliceforms/Dec-13-2007_02:21:10: + 6:Error Details: /work/cgi-bin/BulkGO.cgi:If any individual load errors occured, they w +ill be listed here:</b><p> /work/GOBKTProject/cgi-bin/TitleLiner.cgi-ELFE-fixed:# Lastly, the cou +nt variable logs the result.

where 'BulkGO.cgi', 'TitleLiner.cgi-ELFE-fixed' and 'Dec-13-2007_02:21:10' are file names
File name and path are seprated by ':' from the matching string.
Please help me with a regex, which could seperate all possible file names from such a find | grep result.

Thanking all in advance.

In reply to RegEx to get file name from find results by vsailas

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.