-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2014-04-29 a las 22:03 -0400, Anton Aylward escribió:
I believe someone mentioned that the shell methods treat all whitespace, that is any string of space, tab, newline, as a single separator.
So a file with the name "This\ is\ \t\ a\ \ \ long\nfile\ name" would be output with the "-print" in such a way that it is read into your WORD as either
"This is a long file name" or "This is a long"
depending on whether you piped or used an intermediate file.
Then I will not us use "-print" :-) The way I'm doing it I get the right number of spaces and I can access all those files, it appears. I just get a few unintended entries (the parent dirs). I will do a few more tests to verify, though, so thanks :-)
Thus when you tried accessing the file by the name in WORD it would fail.
BTDT.
That's why I use "-print0" and "xargs -0"
Of course people coming from a MS-DOS (and a few other Oss come to that) world don't get to deal with long file names with embedded space :-)
I do have a lot of long file names with spaces in them, several some times :-) - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlNgX48ACgkQja8UbcUWM1wTSAD/Qm1KZMVeWLn4Zrj5MBrKyn03 KJPhmbFVgUqe6xTbEYYA/3kLO2IETamjfpv7go45vkgMqALcOI0KoHvF52SeyIkn =O7/a -----END PGP SIGNATURE-----