https://bugs.kde.org/show_bug.cgi?id=361760

            Bug ID: 361760
           Summary: Find/Replace in Files : Failed: no files found
                    matching the wildcard patterns
           Product: kdevelop
           Version: git master
          Platform: Compiled Sources
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: rjvber...@gmail.com

Under certain conditions, the Find/Replace in Files function fails to find any
files matching the wildcard pattern. This happens for me when I use rather
complex paths that are a result of building using a certain distribution
system, but I think that shouldn't matter.

I'll present an example for marble that should be reproducible.

Reproducible: Always

Steps to Reproduce:
A
1. Create a work directory called, for instance,
/opt/local/var/macports/build/_opt_local_site-ports_kf5_kf5-marble/kf5-marble/work
2. unpack the marble sources into
/opt/local/var/macports/build/_opt_local_site-ports_kf5_kf5-marble/kf5-marble/work/marble-15.12.3
3. launch kdevelop5
4. open
/opt/local/var/macports/build/_opt_local_site-ports_kf5_kf5-marble/kf5-marble/work/marble-15.12.3/CMakeLists.txt
5. accept the proposed build directory,
/opt/local/var/macports/build/_opt_local_site-ports_kf5_kf5-marble/kf5-marble/work/marble-15.12.3/build
6. complete the project import
7. right-click on an entry in the project view, select Find/Replace in this
folder and do a search on a string that is guaranteed to exist in the project.

Actual Results:  
KDevelop will spend some time "collecting files", and then present the message
that no files are found that match the wildcard pattern.

Expected Results:  
search results showing all occurrences of the given search string

- this has been the case since KDevelop 4.7 at least

- Workaround:
1. Close the project in KDevelop
2. move the source directory
(/opt/local/var/macports/build/_opt_local_site-ports_kf5_kf5-marble/kf5-marble/work/marble-15.12.3/)
to a location with a shorter path, say $HOME/src/marble-15.12.3
3. ln -s $HOME/src/marble-15.12.3
/opt/local/var/macports/build/_opt_local_site-ports_kf5_kf5-marble/kf5-marble/work/marble-15.12.3
4. reopen the project (via Recent Projects)

A priori the search function should work correctly now.

- Most likely unrelated, but it seems the cmake importer wizard offers the 1st
cmake exec found in the path rather than the version selected in the KDevelop
settings.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to