4 ms·
<file is allowed to be at front (for some reason it seems counterintuitive, but '<file grep foo' is valid) Still 'useless use of x' complaining doesn't make mu
by garaetjjte 6y ago
<file is allowed to be at front (for some reason it seems counterintuitive, but '<file grep foo' is valid)
Still 'useless use of x' complaining doesn't make much sense for me, unixy tools are generally used in pipelines, using separate tools makes each step more clear, easier to modify pipeline. I don't have to skim through pages of extra grep/whatever tool manual just to check if it maybe reimplemented wc -l
- aasasd 6y ago> unixy tools are generally used in pipelines Yeah, for this reason I won't write ‘<file’ at the front even though I've heard of it before. I'm in the Unix game for good command-line pipelines among other things, and bending over backwards to sidestep the pipeline isn't really in my plans.
- dllthomas 6y ago<bucket hose | hose | hose vs hose <bucket | hose | hose
- dllthomas 6y agoSomething I like about putting my redirections at the front is that if I pull this out into a function there often is no redirection, or the redirection will take the form of an `exec` on an earlier line. In either case, keeping the redirection out of the pipeline proper makes that transformation easier.
- deleted 6y ago[deleted]