|
|
Watch for undocumented behavior of cp -R
Some say this is the way it should work. Others say they hate it this way.
If you don't like it you can always right a script to strip the trailing slash and then alias "cp -R" to it. Someone might want to tweak this further to ensure things like options are being passed down correctly. The point is, Unix is designed to be tweaked. It gives you the most possible options and then lets you customize for your own needs. Don't let it dictate how you use it.
Yes!
What he said. :)
No!
After many years of sysadmin'ing, I ended up forsaking almost all such customizations, for the simple reason that I couldn't help out any of my users if I was too habituated to something nonstandard. Nor did I feel like running classes on 'suggested hacks for your initfiles'.
Jef Raskin, in his excellent The Humane Interface, goes into this whole area in more detail, but the short version is "if the system requires customization, then it is poorly designed." In a similar vein, he argues against giving users (even expert users) multiple ways of getting the same thing done -- the cognitive overhead of figuring out which one to use is surprisingly large. None of this is to argue that customizability, per se is evil, but that using it to paper over fundamental design flaws is. Some days un*x seems to me to be one huge design flaw ... Raskin's book is available from Amazon.
Watch for undocumented behavior of cp -R
This is a nice workaround, but shouldn't the code be this?: |
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.08 seconds |
|