- Nov 2020
Man, for some reason, I really like this answer. I recognize it's a bit more complicated, but it seems so useful. And given that I'm no bash expert, it leads me to believe that my logic is faulty, and there's something wrong with this methodology, otherwise, I feel others would have given it more praise. So, what's the problem with this function? Is there anything I should be looking out for here?
I think the main thing wrong with it is the eval (which I think can be changed to
$("$@")and it's pretty verbose.
Also, there are more concise ways to do it that would probably appeal more to most bash experts...
like set -x
and it does unnecessary things: why save output to a variable? Just let output go to where it would normally go...
So yeah, I can see why this solution isn't very popular. And I'm rather surprised by all the praise comments it's gotten.
- hasn't caught on / gained popularity
- why isn't this more popular?
- why isn't this more common/the norm?
- why aren't people talking about/asking this?
- good point
- good question
- Oct 2020