Nicolas Williams wrote:
> On Mon, Mar 29, 2010 at 12:23:56PM -0400, Sebastien Roy wrote:
>
>>> Is there any escaping of whitespace and non-printable characters in the
>>> pathnames? If not then the above format is ambiguous and cannot be
>>> safely scripted.
>>>
>> Taking a step back here, this subcommand is not the only zfs
>> subcommand whose output could be subject to parsing by scripts.
>>
>
> Many zfs sub-commands already have a -H option ("Display output in a
> form more easily parsed by scripts").
>
However, those subcommands don't deal with filenames. They deal with
things like filesystem names and property names/values, which are all
much more constrained than filenames.
How do commands like ls and find handle printing of filenames with
arbitrary characters (newlines and such)?
--matt
