In general, it has great mechanical sympathy. You need to split your larger problem into smaller sub-problems, and then figure out which sub-problems depend on each other using the recursive formulation. Once you have…
Its actually part of the POSIX standard that redirections can be put anywhere in the command line, so one can do: <file.txt sed 's/some/filter' | other_cmd on any standard compliantish shell :) (I use zsh, and I know it…
At least for the PATH, you can also automate the looking. When on a new POSIXy system, I usually try "(IFS=: ; ls $PATH)" at the shell to get a listing of all programs available.
In general, it has great mechanical sympathy. You need to split your larger problem into smaller sub-problems, and then figure out which sub-problems depend on each other using the recursive formulation. Once you have…
Its actually part of the POSIX standard that redirections can be put anywhere in the command line, so one can do: <file.txt sed 's/some/filter' | other_cmd on any standard compliantish shell :) (I use zsh, and I know it…
At least for the PATH, you can also automate the looking. When on a new POSIXy system, I usually try "(IFS=: ; ls $PATH)" at the shell to get a listing of all programs available.