Written by petko10 the 17 Jan 12 at 22:33.

Upon installation or right thereafter the fixed mount point devices (NOT random removable media,etc..) should be scanned and catched , so that the dash could be used to do a full search for files (because now it's just silly , to search in some recent files- not useless , but not fully functional) .
To make this option better - there should be a simple configuration of folders to include or exclude of scanning . And also a rescan option .

Upon installation or right thereafter the fixed mount point devices (NOT random removable media,etc..) should be scanned and catched , so that the dash could be used to do a full search for files (because now it's just silly , to search in some recent files- not useless , but not fully functional) . To make this option better - there should be a simple configuration of folders to include or exclude of scanning . And also a rescan option .

Written by petko10 the 19 Jan 12 at 07:25.

Since in the past there were problems with indexing everything I propose having a simple configuration of the search - a menu in System settings to set folders to be indexed and to order rechecking .

Since in the past there were problems with indexing everything I propose having a simple configuration of the search - a menu in System settings to set folders to be indexed and to order rechecking .

Written by gleedadswell the 24 Jan 12 at 01:16.

I realize that the command line locate command isn't always ideal for this, because when the files are changing a lot the user would need to run updatedb repeatedly, which often isn't an option because it requires super user privileges. Could a limited updatedb, that only scans inside the user's own directories, be made available to the user. Then have the dash-search able to run this limited updatedb and to run a locate, perhaps as an alternative to the current search function?

I realize that the command line locate command isn't always ideal for this, because when the files are changing a lot the user would need to run updatedb repeatedly, which often isn't an option because it requires super user privileges. Could a limited updatedb, that only scans inside the user's own directories, be made available to the user. Then have the dash-search able to run this limited updatedb and to run a locate, perhaps as an alternative to the current search function?

Written by PaddyLandau the 24 Jan 12 at 17:32.

Once the database has been updated, setting inotify (or incron or equivalent) to watch for changed files is efficient. The database does not have to search for changes, but instead will respond to changes when they happen.

The database need search for changes only if the partition has been changed by something when the database has not been active (e.g. when using a Live CD or after using Recovery mode).

This gives you the best of both worlds: comprehensive, always up-to-date, and fast.

Once the database has been updated, setting inotify (or incron or equivalent) to watch for changed files is efficient. The database does not have to search for changes, but instead will respond to changes when they happen. The database need search for changes only if the partition has been changed by something when the database has not been active (e.g. when using a Live CD or after using Recovery mode). This gives you the best of both worlds: comprehensive, always up-to-date, and fast.