[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Some questions regarding development for KDE3
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-01-18 22:07:18
Message-ID: 20070118220718.GA6861 () morpheus ! apaku ! dnsalias ! org
[Download RAW message or body]

On 18.01.07 22:54:43, Guillaume Laurent wrote:
> On Thursday 18 January 2007 20:29, Matthew Woehlke wrote:
> > Guillaume Laurent wrote:
> > > - 'Find in Files' merely calls /usr/bin/find ?? You've got to be kidding
> > > here, I suppose it's just a temporary fill-in until the real feature is
> > > done.
> >
> > *You're* kidding here, right? What on *earth* would we write ourselves
> > that would be more powerful than 'find'?
> 
> Gee, I don't know, something like Eclipse's indexing feature perhaps ?

And thats probably a reason why eclipse is so bloated. Why is find a
problem? Sure the first find of the day on a large project is a bit
slow, but all others are pretty fast (at least for me on kdev sources).

> > > And it doesn't keep the previous searches in memory.
> >
> > Huh? I have no idea what you mean...
> 
> Eclipse keeps a history of searches and lets you display the previous ones 
> very easily.

KDevelop does store the result of old searches by putting each result in
a separate tab in the find in files toolview.

And of course you can access old search patterns in the dialog.

Andreas

-- 
Break into jail and claim police brutality.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]