First off, use strict warnings and diagnostics or die even for code of this size. You had a typo with @nowshow that strict would have picked up. One might also want to consider use CGI or die; if this project involves handling form input. If this is all that it is, though, you might be able to escape without using it.

All that aside, I'd probably do something like:

#!/usr/bin/perl -w use strict; print "Content-type: text/html\n\n"; opendir(DIR,"./") or die "Couldn't open directory"; my @files = readdir(DIR); closedir(DIR); my @noshow = (".", "..", __FILE__); foreach my $f (@files) { print "$f<br>\n" unless grep {$f eq $_} @noshow; }

perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'


In reply to Re: list dir contents, w/o some stuff by Chmrr
in thread list dir contents, w/o some stuff by einerwitzen

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.