exec can be given arrays, so you don't need to quote arguments.

to get the pipe open behavior you can pipeopen ls, and then exec the pager: 

open STDIN, "-|", ...;
exec @pager;

[download]
FYI, that is how the shells do it: they create the pipeline descriptors, fork off children for the processes, dup the filedescriptors to stdin/stdout as appropriate, and then exec the subproccesses.

If you insist on quoting and concatenating there are cpan modules to do this more safely.

map { } in void context is silly: 

$_ = qq{"$_"} for @ARGV;

[download]
To check if you have less, don't make assumptions based on the platforms. Instead: 
use File::Which;
my $pager = which("less") || which("more") || die "no pager";

[download]

Lastly, all of this could be completely superceded with a shell alias =)

-nuffin
zz zZ Z Z #!perl

In reply to Re: expanded "ls" by nothingmuch
in thread expanded "ls" by blahblahblah

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.