René Scharfe <l.s.r@xxxxxx> writes: > Would it make sense to have a --paths-file parameter instead that allows > reading paths from a given file and honors the convention of reading > from stdin with the special argument "-"? Reading from stdin would > still only work for one parameter at a time, but paths could also be > passed via a regular file or named pipe, allowing for more flexibility. The command's primary function itself may want to use the standard input stream to read things other than the list of paths; if we are not limiting ourselves to plumbing (i.e. doing one thing well), the "--stdin-paths" may not be a general solution that is good enough. So, reading paths from a file (which could be "-" as you suggest) would be a good solution for that.
