Re^6: redirect output from a command to another command

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.

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

Replies are listed 'Best First'.
Re^7: redirect output from a command to another command by DrHyde (Prior) on Mar 07, 2011 at 11:45 UTC
I suggest that you click the "in reply to" link on this post, and then on the page that takes you to, and so on. Then you will be enlightened.	[reply]
Re^8: redirect output from a command to another command by ikegami (Patriarch) on Mar 07, 2011 at 16:08 UTC
No solution was given in any ancestor to your post. I don't even know what you're disagreeing with. I humoured your games, but now it's time for you to be clear. Do you disagree with any of the following? Your bash was incorrectly built. Your bash being incorrectly built does not speak to the portability of the /dev/fd method. The portability of the /dev/fd solution is not related to the portability of bash. /dev/fd is not portable between OSs or even between systems with the same OS. Named pipes are quite portable. If so, let's discuss that. If not, then we're off topic.	[reply]
Re^9: redirect output from a command to another command by DrHyde (Prior) on Mar 08, 2011 at 11:29 UTC
No solution was given in any ancestor to your post. Apart from redirect output from a command to another command. I don't care whether my bash was correctly built, because it's as supplied by the vendor. That a vendor supplies what you deem to be a broken shell demonstrates that `diff <(echo -e "oranges") <(echo -e "apples")` can't really be relied on. That it also doesn't work in some non-bash shells also demonstrates that, as I said in node Re: redirect output from a command to another command "it's a neat trick, but I'd only use it in shell prompt one-liners, not in scripts that might get used elsewhere". All I was doing was pointing out that the shell version that started this thread isn't that great. All consequent discussion has been because of your misunderstanding of what I was commenting on.	[reply] [d/l]
A reply falls below the community's threshold of quality. You may see it by logging in.