On Mon, 4 Mar 2002, Heinz Nabielek wrote:
> # find /Users/heinz/ -name "kersten*"
> /Users/heinz//Pictures/kersten.pdf
>
> # find /Users/heinz/ -name "Kersten*"
> /Users/heinz//Documents/Kersten.jpg
>
> What is the meaning of the double slashes?
> (Perhaps more Darwin than fink specific?)
This is a property of the 'find' command -- feed it a directory name and
it will start from there & descend recursively. If that directory has a
trailing slash, as in this case, then it will be used in the generated
list that you get from the command. Compare & contrast:
# find /Users/heinz -name "kersten*"
/Users/heinz/Pictures/kersten.pdf
# find /Users/heinz/ -name "kersten*"
/Users/heinz//Pictures/kersten.pdf
# find /Users/heinz -name "Kersten*"
/Users/heinz/Documents/Kersten.jpg
# find /Users/heinz/ -name "Kersten*"
/Users/heinz//Documents/Kersten.jpg
In every case I've come across so far, the doubled slash is Mostly
Harmless -- a bit like saying "cd ." would be mostly harmless. If you're
doing any automagic processing of the list that 'find' gives you, it might
not be a bad idea to avoid that extra slash by leaving it off the initial
directory name[s], but I haven't come across any situations where it hurt
anything to leave it in there.
--
Chris Devers [EMAIL PROTECTED]
Apache / mod_perl / http://homepage.mac.com/chdevers/resume/
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
