Re: Files not found
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
- Date: Sat, 8 Mar 2008 15:41:50 -0600
"John" <nyrinwi@xxxxxxxxx> wrote in message
news:47d2a3e5$0$4968$4c368faf@xxxxxxxxxxxxxxxxx
files=$(find ./ -cmin -5 -print)
or if you prefer an array...
files=($(find ./ -cmin -5 -print))
You can then take whatever action you like; e.g.
if [ ${#files} -eq 0 ]; then ... # non array
I tried this, and it doesn't work, either. It gives me an error, saying:
../Videoscribe: line 23: unexpected EOF while looking for matching `)'
Line 23 is the if [ ${#files} -eq 0 ] statement.
Then it says:
../Videoscribe: line 33: syntax error: unexpected end of file
The script Videoscribe only has 32 lines.
If I remove the if [ ${#files} -eq 0 ]; then ... fi section, the errors
disappear.
Other than as a comment delimiter, I am not familiar with the use of #
within an evaluation expression. What does it do?
.
- Follow-Ups:
- Re: Files not found
- From: John
- Re: Files not found
- References:
- Files not found
- From: Leslie Rhorer
- Re: Files not found
- From: John
- Files not found
- Prev by Date: Re: Files not found
- Next by Date: Become crorepati in a less than year time by trading into indianstock mkt option
- Previous by thread: Re: Files not found
- Next by thread: Re: Files not found
- Index(es):