in reply to Re^2: redirect output from a command to another command
in thread redirect output from a command to another command

Then it was incorrectly configured by the OS vendor.

But in any case, even if all bash users were to upgrade to the latest and greatest bleeding edge version, and spend hours tweaking obscure configuration options, that solution still wouldn't be portable, as it doesn't work in some other shells.

  • Comment on Re^3: redirect output from a command to another command

Replies are listed 'Best First'.
Re^4: redirect output from a command to another command
by ikegami (Patriarch) on Mar 03, 2011 at 17:06 UTC

    It has nothing to do with the shell. No shell is used by the Perl code I used. It's an OS feature.

    And yes, it wouldn't be portable to other OSes (or differently setup OSes, based on your experience). I didn't mean to imply otherwise.

[reply]

      You were talking about my shell being broken. It is therefore OBVIOUS that I was talking about the shell code that started this thread and not your perl code, and it therefore has everything to do with the shell.

      If you bothered to pay attention you will also have noticed that I didn't even respond to your post that had perl code in it.

[reply]

        If you bothered to pay attention you will also have noticed that I didn't even respond to your post that had perl code in it.

        One of the solution (named pipes) proposed is portable, the other was the Perl code. So to which solution were you referring if you weren't responding to the post that had the Perl code?

        You were talking about my shell being broken.

        Yes, until you said the solution wasn't portable. It (the solution) has nothing to do with the shell.

[reply]

In Section Seekers of Perl Wisdom