On 20.09.13 19:18, Trent W. Buck wrote:
> Erik Christiansen writes:
>
> > ยน And my software teams were blessed with *nix servers all that time
> > too, though many members used the other OS on their machines.
>
> VMS?
OK, once (in the early days) there was a third OS involved - one team
member was putting Mac documentation files onto the *nix server via NFS.
All those "resource" files, one for each data file, stuffed into a
parallel ".resource" directory at each directory level, were something
that surfaced when I ran an audit script.
Rather than running around trying to catch every kind of cruft, I chose
to keep it out, because there's enough productive work to do already.
That said, I have once or twice used -print0 with find and xargs, but
only when dealing with foreign material. And tabbing for filename
completion in bash will escape the space characters, to allow the
command line to work ... but that just confirms how alien such filenames
are to a space delimited command line.
The couple of curiously emotional posts on this thread, do seem to
reveal a lack of scripting (and possibly even command line) experience,
because having to quote "filenames with real space characters in them",
in order to avoid the CLI barfing, tends to clarify that they are alien.
The CLI cannot deal with them, and it is only our protective
work-arounds which allow them to be tunnelled in a script.
Those of us old enough to remember the days when "no spaces in
filenames" was accepted *nix practice, remember them with fondness,
but s/ /_/g will do me.
Erik
--
Whenever people agree with me I always feel I must be wrong.
- Oscar Wilde
_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main
