Perhaps you should just try it?

> { echo out; echo err >&2; } >f1 2>&1
> cat f1
out
err
> { echo out; echo err >&2; } 2>&1 >f1
err
> cat f1
out

[download]

Redirection order definitely DOES matter in the shell. (Hmm, unless it's shell-specific? I'm using bash)

And just to do exactly what you said..

> perl -e'print "print\n"; warn "warn"' >f1 2>&1
> cat f1
warn at -e line 1.
print
> perl -e'print "print\n"; warn "warn"' 2>&1 >f1
warn at -e line 1.
> cat f1
print

[download]

In the first case both print and warn go to the file, in the second case warn goes to stdout and print to the file.

In reply to Re^3: capturing stderr of echo piped to a file by Crackers2
in thread capturing stderr of echo piped to a file by cebundy

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.