Put the return value from ls into a variable, and filter the file names for the extensions you want to allow. It's better to do it this way than filtering through ls, imho.

EDIT: Here's some code: 

#!/usr/local/bin/perl

use strict;
use warnings;

my $base = '/u/web/user/';
my @allow = qw/log txt sql err par csv/;
my $e;

print "Content-type: text/plain\n\n";
for (split /\n/, `ls -lt $base`) {
    for $e (@allow) {
        if (m/\.$e$/) {
            print "$_\n"; last;
        }
    }
}

[download]
The advantage of doing it this way is that your code is easy to modify to work with rejected lines, should you decide you want to in the future.

In reply to Re: Outputting contents of ls -lt by TedPride
in thread Outputting contents of ls -lt by mh53j_fe

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.