Dennis Smit <[EMAIL PROTECTED]> wrote: > previous week we were discussing the du, wc --files-from options > which didn't lead to much result. However I've got the FSF > license post on it's way so i would love to put some work > in this. > > I'am still in favor for Pauls idea to have a --files-from=NAME and > a --null option were --files-from reads newline terminated and > --null added makes it read NULL terminated, however if for some > reason --files-from=NAME that reads NULL terminated without the > --null option is prefered it's naturally ok with me.
And I'm still reluctant to allow --files-from without --null. It's too easy for people to forget that a single file with a name containing a newline can cause that not to work. Note that this option is *not* intended or even necessary for most cases where people would be saving a list of inputs to a file and reading or editing it. If you have such a list that is so long that you can't put the names on a single `du' command line, then (assuming no file name contains a newline) just pipe the list through e.g., cat YOUR_LIST | tr '\n' '\0' | du --null --files-from - There is also the question of what to name the option that selects NUL-terminated *output* lines. Suggestions welcome. > Also, Jim did you have a look at my df -c --total patch ? is > it alright and can it be included when i signed the FSF > papers ? I've just replied. _______________________________________________ Bug-coreutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-coreutils
