> pattern before. I never knew it expanded the wild card before it
> searched. Gotta be the old DOS mentality.
Actually, no. It is the *shell* that expands the wildcard on a
unix-system. If you want to pass a wildcard to a program, you have to
explicitly make it clear to the shell *not* to expan
On Thu, 8 May 1997, Rick Jones wrote:
> This is interesting:
>
> panther# pwd
> /usr/src/kde/kdelibs
> panther# find /usr -iname kfdial*
> /usr/src/kde/kdm-0.4.4/kgreeter/kfdialog.cpp
> /usr/src/kde/kdm-0.4.4/kgreeter/kfdialog.moc
> /usr/src/kde/kdm-0.4.4/kgreeter/kfdia
tes, the kfdial* argument MATCHES the file kfdialog.cpp
> in the current directory (/usr/src/kde/kdm-0.4.4), and that is what is
> passed to find as an argument.
>
> You're even taking advantage of this behaviour when you issue commands
> like "cd ../kdm*"
>
&g
kdm*"
> [...deleted...]
>
> Now why can't "find" see the kfdialog.h/.moc files from the kdm directory
> but it sees them from kdelibs directory?
>
> I am not happy about this. Does anybody have a clue?
it's not a problem with find, it's a probl
This is interesting:
panther# pwd
/usr/src/kde/kdelibs
panther# find /usr -iname kfdial*
/usr/src/kde/kdm-0.4.4/kgreeter/kfdialog.cpp
/usr/src/kde/kdm-0.4.4/kgreeter/kfdialog.moc
/usr/src/kde/kdm-0.4.4/kgreeter/kfdialog.h
/usr/src/kde/kdm-0.4.4/kfdialog.cpp
panther# cd ../kdm*
panther# pwd
/usr
5 matches
Mail list logo
