[Controversial Patch for Bug 18180] kfind sloppy match for simple search strings

[Thomas Zander]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 20 July 2002 00:41, Martin Konold wrote:
> On Friday 19 July 2002 06:24 pm, Kurt Granroth wrote:
> > On Friday 19 July 2002 03:47 am, konold at mail.kde.org wrote:
> > > On Fri, Jul 19, 2002 at 12:36:05PM +0200, Klas Kalass wrote:
> > > > > > k?ind -> kfind.cpp is NOT FOUND
> > > > > > k?ind* -> kfind.cpp is FOUND
> > > >
> > > > I am not quite sure I understand: The syntax *is* command line
> > > > wildcards plus the special case that no wildcards specified is
> > > > interpreted as "*<searchstring>*" so that users not knowing about
> > > > wildcards have an easier
> > >
> > > At least the example says that k?find.cpp does not match kfind.cpp but
> > > k?find* does match. This example contradicts your explaination.
> >
> > No, he said that 'k?find' does not match 'kfind.cpp' (which is right).
>
> this is fine but he also said (look above!) that k?ind* does match
> 'kfind.cpp' which of course is inconsistent simply because
> anythingnonmatching* should never match.
>
> Regards,
> --martin

ls disagrees with you:

zander at dumas:Desktop$touch kfind.cpp
zander at dumas:Desktop$ls k?ind*
kfind.cpp


- -- 
Thomas Zander                                           zander at planescape.com
                                                 We are what we pretend to be
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD4DBQE9OHfkCojCW6H2z/QRArEZAJ46Fp+adAelxGinzbgQOPFIKDad5wCXRasm
pPYGkcuyjK8tIeAvAVrCXg==
=QPAg
-----END PGP SIGNATURE-----