https://bugs.kde.org/show_bug.cgi?id=361760
Igor Kushnir <igor...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In| |5.14
Latest Commit| |https://invent.kde.org/kdev
| |elop/kdevelop/-/commit/2ced
| |983d4975cedb5166c4115397870
| |aaab0e148
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #5 from Igor Kushnir <igor...@gmail.com> ---
Git commit 2ced983d4975cedb5166c4115397870aaab0e148 by Igor Kushnir.
Committed on 15/01/2024 at 11:44.
Pushed by igorkushnir into branch 'master'.
GrepFindFilesThread: match relative paths against Exclude filter
Two KDevelop users have reported the "No files found matching the
wildcard patterns" bug when the project directory is within a parent
directory named "build". The /build/ pattern is present in the default
Exclude filter. Therefore, all absolute file paths in such a project
directory match the default Exclude filter and are not searched in.
Match paths relative to the current search location in order to fix the
bug.
A downside of this fix is that when multiple projects are open,
excluding one of them from the search is no longer possible. Hopefully
this is a very rare use case.
FileFinder::findFilesCanonical: don't search in a subdirectory whose
relative path matches the Exclude filter. Since the relative path to a
file within a subdirectory contains the relative path to the
subdirectory, it would also match the Exclude filter and therefore would
not be inserted into the results list.
FIXED-IN: 5.14
M +45 -8 plugins/grepview/grepfindthread.cpp
M +1 -1 plugins/grepview/grepfindthread.h
https://invent.kde.org/kdevelop/kdevelop/-/commit/2ced983d4975cedb5166c4115397870aaab0e148
--
You are receiving this mail because:
You are watching all bug changes.
