use Perl

• Funny redirecting? (Score:1)

  by DiamondInTheRough (4076)

  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.
  • Re:Funny redirecting? (Score:2)

    by nicholas (3034) <nwc10+useperl@colon.colondot.net> on 2009.08.11 12:44 (#69975) Homepage Journal

    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 parsed as

    1. Redirect stderr to a dup of stdout (which happens to be a pipe, not a tty)
    2. Redirect stdout to /dev/null
    3. Redirect stdin from /dev/null

    At which point no file descriptor that git can see is a tty (in case it behaves differently, à la git log), but stderr is still open so I can follow advice from Klortho [google.com] 11906, 11914, 11919, 11920, and especially 11922 :-)

    At which point I want the command to get the hint and be silent, dammit, if nothing is wrong, but it's simply not taking the hint. :-(

    Reply to This

    Parent

    • Re: (Score:1)

      by DiamondInTheRough (4076)

      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.