After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 346772 - beagle backend is not strict about given directory names
beagle backend is not strict about given directory names
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: File Search Interface
2.15.x
Other Linux
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-06 14:51 UTC by Daniel Holbach
Modified: 2010-10-16 02:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Holbach 2006-07-06 14:51:43 UTC 
Forwarded from: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/51144

Binary package hint: nautilus

When searching files with beagle enabled, I can add additional search criteria to the search. If I add a directory to search in, in my case 'gajim', I always get results from 'gajim-trunk' and all other directories beginning with 'gajim' (the dirs being one level above with gajim in their name get displayed as well). It seems like the dir is added to the beagle search and therefore does substring search as well?
The directories are in my home dir like this:
~
  -- gajim
  -- gajim_trunk
  -- ...
I expected files to only be displayed from inside 'gajim'.
Comment 1 Fabio Durán Verdugo 2010-09-04 04:08:00 UTC 
This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it.
Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field?

Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE after 6 weeks.
Comment 2 Fabio Durán Verdugo 2010-10-16 02:03:49 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!