Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Uh... wouldn't "2>&1 >/dev/null" just put what's going to stderr to stdout and what's going to stdout to nothing, as opposed to both stderr and stdout to nothing?

    I think you need "2>/dev/null" for what you want.

    --
    The new Strawberry Perl for Windows has been released! Check http://strawberryperl.com for it.
    • Uh... wouldn't "2>&1 >/dev/null" just put what's going to stderr to stdout and what's going to stdout to nothing, as opposed to both stderr and stdout to nothing?

      Yes.

      I think you need "2>/dev/null" for what you want.

      No. :-)

      I'm relying on the order of parsing of pipes and redirection. git fetch -q 2>&1 >/dev/null </dev/null | cat is parsed as run this:

      git fetch -q 2>&1 >/dev/null </dev/null

      piped to that:

      cat

      Then, git fetch -q 2>&1 >/dev/null </dev/null is

      • Sorry. Misunderstood what you meant, then. Better answers are below.
        --
        The new Strawberry Perl for Windows has been released! Check http://strawberryperl.com for it.