On 17/07/14 21:51, Brett Pemberton wrote:
On Thu, Jul 17, 2014 at 9:35 PM, Daniel Jitnah <djitnah@greenwareit.com.au> wrote:
I'd have the same response to someone using _ instead of a space. Why bother? May be because:
danyj@git-deb7-64:~/test$ touch windows danyj@git-deb7-64:~/test$ touch 7 danyj@git-deb7-64:~/test$ touch windows\ 7 danyj@git-deb7-64:~/test$ ls -l total 0 -rw-r--r-- 1 danyj danyj 0 Jul 17 21:23 7 -rw-r--r-- 1 danyj danyj 0 Jul 17 21:23 windows -rw-r--r-- 1 danyj danyj 0 Jul 17 21:23 windows 7 danyj@git-deb7-64:~/test$ rm -rf windows 7 danyj@git-deb7-64:~/test$ ls -l total 0 -rw-r--r-- 1 danyj danyj 0 Jul 17 21:23 windows 7 danyj@git-deb7-64:~/test$
Sorry, I'm honestly at a loss as to what you were demonstrating there.
Ehm, he is demonstrating that bash command line utilities become easily confused then using files with spaces in their names. What was asked? 1.) to delete the file windows 7 What happened? 1.) the files windows and 7 were deleted See, it does matter! cheers Robert
Let's do the same thing, but with underscores.
brett@capsid:/tmp/space$ touch windows brett@capsid:/tmp/space$ touch 7 brett@capsid:/tmp/space$ touch windows_7 brett@capsid:/tmp/space$ ls -l total 0 -rw-rw-r-- 1 brett brett 0 Jul 17 21:50 7 -rw-rw-r-- 1 brett brett 0 Jul 17 21:50 windows -rw-rw-r-- 1 brett brett 0 Jul 17 21:50 windows_7 brett@capsid:/tmp/space$ rm -rf windows 7 brett@capsid:/tmp/space$ ls -l total 0 -rw-rw-r-- 1 brett brett 0 Jul 17 21:50 windows_7 brett@capsid:/tmp/space$
In both cases, it did exactly what we asked it to. Spaces had absolutely no bearing on anything.
/ Brett _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main