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

[Klas Kalass]

Am Freitag, 19. Juli 2002 11:08 schrieb Martin Konold:
> On Thursday 18 July 2002 10:28 pm, Klas Kalass wrote:
>
> Hi,
>
> > Example:
> > kfind -> kfind.cpp is FOUND
> > k?ind -> kfind.cpp is NOT FOUND
> > k?ind* -> kfind.cpp is FOUND
> > .c -> kfind.cpp is FOUND
> > *.c -> kfind.cpp is NOT FOUND
> >
> > May I apply?
>
> Hmm, I do not feel comfortable. On one hand the rules look arbitrary but
> try to guess what people really meant. Due to the high number of
> documentation and knowledge I prefer a syntax similar to the command line
> wildcards.
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 
time searching for files and users knowing about wildcards can still do 
fairly exact searches.
Do you have an idea how to resolve the conflicting interests in this case in a 
better way?

Cheers,
Klas