--fields opt to
So my cut manpage says it supports the following:
Looking through our scripts (
They can of course be left for later.
A couple of ways this implementation is different to
and the fields may be printed out more than once:
Seems more versatile to me this way - any thoughts?
Trying to think of whether there any possible gotchas to the end-user doing it this way...
So the use case shows a problem with this: You're gonna use it like
Otherwise I think you got it. Returning 1 if nothing happened is what string tends to do, and so far it has worked well. Reordering seems useful, and it's a good feature.
I guess I could add an option
Also I instead found more cases (for completions anyway) look like this:
Where it wouldn't be all that different after:
Note: I have not yet implemented the "2-" syntax