On 04/29/2014 10:27 PM, Carlos E. R. wrote:
The way I'm doing it I get the right number of spaces and I can access all those files, it appears.
You probably don't have the kind of file names I described, though :-) May people do shell programming as a 'suck it and see' iteration such as this thread has addressed. In the 80% case it works and you sometimes, as this thread has covered, learn along the way. But sometimes there are errors because things don't who up. Some of those pernicious file names are an example of that. I got BTDT'd when doing a backup. A file with a double space "\ \ " didn't get backed up. If course it was an important file. You live and learn though making mistakes. Hopefully the mistakes aren't too serious and its best if you can learn from the mistakes of others. I learnt early one a few important principles, despite resistance from my peers and managers: Context is Everything Generalise and parametrise Document everything, especially the design decisions Solve the right problem If it gets too difficult or too complex then you're doing it wrong "Form follows Function" - Loius Sullivan, 1896 Reduce 'ripple effect' by reducing coupling -- Overcoming Water overcomes the stone; Without substance it requires no opening; This is the benefit of taking no action. Yet benefit without action, And experience without abstraction, Are practiced by very few. -- Lao Tse, "Tao Te Ching" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org