IMO, when you need to "grep" stuff, you're better off doing it in perl. I'm agnostic about shell "du" vs. perl-module solutions for the same thing, but stringing a bunch of separate "grep" commands in a pipe like the OP does is just ugly and so unnecessary. I'd be content with something like this (not tested): 
$du = join( '',
            grep !/^.*?Maildir.*?(?:cur|tmp|new|courierimapkeywords)$/
+,
            `du -ch $homedir` );

print $du;

[download]
Anything you can do to shorten/constrain/simplify the stuff in backticks is generally a good idea, esp. in terms of eliminating "shell-magic" characters as much as (or completely if) possible.

In reply to Re: du with backticks by graff
in thread du with backticks by Panasonictoilet

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.