Quote:
abuse (verb): to use wrongly or improperly. My use of the word was correct. |
Quote:
|
Quote:
Code:
/usr/bin/find /tmp -mindepth 1 -maxdepth 1 -delete |
I have a 250GB hard drive:
20GB /root 1GB swap 1.5GB tmpfs (default) remaining GB /home Sometimes I remove /tmp/SBo/ but everything else in it remains. Gives me a quick view of the extra stuff I have installed. That and my /home/Slackbuilds directory. Doesn't get in my way a bit. |
Quote:
|
Quote:
|
Quote:
|
Quote:
I tried touch foo\nbar , touch foo\\nbar , touch "foo\\nbar" , touch "foo\nbar" , without success. I was looking at the ls options again, and there is this option "-Q" (and --quoting-style=WORD) that I think is very usefull, it encloses the names with spaces in double (or single) quotes. Sorry if this is a little bit off-topic. |
Quote:
Code:
touch $'foo\nbar' |
Quote:
Code:
paulo@paulo:~/Isos$ touch $'foo\nbar' Code:
paulo@paulo:~/Isos$ rm 'foo |
Quote:
Quote:
Quote:
|
Quote:
|
Paulo2, may be my bash-fu is lacking, but I don't see a way around it without find -print0, which is guaranteed to work at least on ext, since the latter forbids zero chars in file names. OTOH, parsing the output of /bin/ls seems like a rather nasty problem, because it separates file names with new lines, and file names may contain new lines, spaces, tabs, quotes, and what have you.
|
Quote:
For example, you can create them with: Code:
touch 'foo Code:
python -c 'open("bar\nbaz", "w")' |
All times are GMT -5. The time now is 10:26 PM. |