[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug in find?
From: |
Jan Meyer |
Subject: |
bug in find? |
Date: |
Fri, 24 Oct 2014 16:57:24 -0200 |
*find* is a Very mature utility, so finding a bug is VERY unlikely, then
again, I can't explain this behaviour:
address@hidden ~/Desktop*
*/xxx $ find /media/jm/Windows -name *.zip*/media/jm/Windows/Program
Files/Arduino/drivers/Old_Arduino_Drivers.zip
/media/jm/Windows/Program Files/Arduino/java/lib/deploy/ffjcext.zip
/media/jm/Windows/ProgramData/AVAST Software/Avast/RemoteCache/jm.zip
address@hidden ~/Desktop*
*/xxx $ find /media/jm/Windows -name *.rar*find: paths must precede
expression: logport.rar
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec] [path...] [expression]
address@hidden ~/Desktop/xxx $ cd ..*
address@hidden ~/Desktop $ find /media/jm/Windows -name address@hidden ~/Desktop
$*
What happens here is that *xxx* holds a file named *logport.rar*, and the
folder above it doesn't. Somehow that affects the output of find. I find
that rather baffling :)
If I stay in *xxx* but delete logport.rar the command works as expected.
Do I get a prize? Or a reprimand? :)
Cheers.
- bug in find?,
Jan Meyer <=