On Fri, 2009-01-09 at 14:08 +0000, Michael Meeks wrote:
So, Morten said I could forward this.
I think it's a highly useful data-point for hacker adoption.
I imagine indexing .c files is a waste of time with beagle, it's for documents - and worse huge, deep source code directory hierarchies - just loading all those dentries & inodes blows your cache and makes ~everything else apparently 'slow'. Until we get a better underlying fs this will always be a problem I think [ btrfs ].
eg. my $ time ls -Rl ~/kde/sources - took:
real 2m11.770s user 0m0.928s sys 0m3.824s
I guess we need a feature to prune all sub-directories of things that look like top-level source-code / project directories. Should prolly get that into FATE.
It would be nice to index HACKING, README, possibly documentation still. Just in case I'm looking for a project maintainer or instructions on how to build foo. Then again, maybe I'm looking for someone's e-mail address and the only place it can be found is in the copyright notice of some .c file :) While I don't think it's a bad idea to short-circuit source code toplevels, I'm worried that a) it won't be enough because there may be other big collections of files that shouldn't be indexed out there and we'll end up with lots of fairly arbitrary rules for what not to index and b) I'm not convinced that people don't search source code for mentions of <foo>. I don't, but then, I don't use Beagle at all. Another, more sophisticated strategy might be to build a list of things to index and prioritize them, so that source directories come last and are indexed at a fairly leisurely pace. It's definitely more work, though. -- Hans Petter -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org