|
|
Standard Behavior
Your proposal of eliminating the directory-contents specifier "
/" and instead choosing files in a directory manually using syntax such as mydirectory/* has the problem of omitting dot files.
Given that this behavior is a long-standing documented feature, this is not a software problem rather it is a user problem. The point of the parent post is to teach folks a command-line nuance, not call for the rewriting of dozens of applications to conform to the limitations of inexperienced users. Learn the trick and move on. :) Michael.
Standard Behavior
Experience or inexperience isn't the issue ... it's GNU-style vs BSD-style. I've spent eight years in GNU-style environments. The first time BSD cp did this to me was really unnerving.
Gnu inconsistent
GNU sometimes ignores the slash and sometimes uses the slash to have such behavious. Compare cp and rsync on GNU and you will see what I mean. At least the BSD pattern is consisent. THat said I never did like that confusion over what / does. I have to re-read the rsync manpage every time I use it!
Gnu inconsistent
rsync is not written by the GNU Free Software Foundation. It is licensed with the GPL. GNU bundles many of the basic command line programs like 'cd, cp, mkdir, rm....' but rsync is written by Andrew Tridgell, the same guy that started the Samba project.
UTSL
Installing GNU cp is counter-productive on Tiger (unlike on Panther) because only the Apple-supplied cp has the resource fork patches.Of course you could submit the appropriate patches to the GNU project or the Fink project (or just patch your own version of /sw/bin/cp) The Apple source code for 'cp' is available from www.opensource.apple.com (cp.c is under "file_cmds"). The code that handles the copying of resource forks is in copyfile.c (which is in "Libc") |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.36 seconds |
|