K find usage?

[John]

Thanks
Shame on me. I'd given up on the ? after finding that it doesn't do anything 
in a number of apps. A pity really because they often tell me exactly what I 
need to know. That is how to use the field/what's in it. Much better than 
wading through the help files which can take ages to load.

I can't see that adding a simple multiple search path would complicate the ui. 
Several paths separated by ; would just mean running kfind again. All the 
typing would be a pain in some case if there was no not option but searches 
could be named and retained as sort of favourites maybe. Not searching a path 
(maybe ;!) shouldn't slow things down much providing it is restricted to 
directory names that are of the root of the search. eg    \;!home;!root etc.

Thanks for the link but I have gained the impression that I would only know if 
it was of much use to me if I loaded it. My impression is that it would be 
useful but will not do what I want. Didn't kfind build a file index at some 
point?

John

On Friday 02 February 2007 13:09, Kevin Krammer wrote:
> On Friday 02 February 2007 13:56, John wrote:
> > This subject is giving me a headache. There doesn't seem to be anyway of
> > getting kfind to only look in certain directories. It will only except
> > one.
>
> Yes, seems to be a limitation. Likely because exposing such a feature could
> result in quite a complex UI
>
> > This isn't a problem off my home directory because I know where things
> > are and don't often have to wait for kfind to sort through 15plus gig of
> > all sorts of things  (very little video etc). It is a problem searching
> > off root as I have to include the home directory. A root search is often
> > needed after I install new applications. I also want to re format 2 hard
> > drives off my home directory. It would be nice to locate all pdf's, docs
> > etc and sort them in one go. Files aren't a problem more than one
> > directory is.
>
> updatedb+locate?
>
> I think there is even a third party KIO slave which lets you
> access "locate"-able files in file dialogs.
>
> > Is there any way of doing this with kfind or is there another application
> > that will. I've looked briefly at beagle but I don't want a dead brained
> > numb skull windoze type solution that assumes I have everything in
> > certain specifically named directories. It just isn't flexible enough and
> > I do hope kde isn't going that way.
>
> The most likely candidate is Strigi, a very nice and fast indexer written
> in pure C++
> http://www.vandenoever.info/software/strigi/
>
> Btw, on your original mail:
> > > > I recently found that I could use kfind to find files with several
> > > > suffixes by entering *.pdf;*.txt;*.doc etc. There is nothing in the
> > > > help files on this general area of use.
>
> The weird thing is that this information is available in the "What's this"
> help, i.e. when one clicks on the question mark icon on the window
> decoration and then on the input field.
>
> You could file a bug report against the KFind documenation
>
> Cheers,
> Kevin

-- 
Regards
John

Suse 10.0
KDE 3.4.2 B
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.