https://bugs.kde.org/show_bug.cgi?id=446404
--- Comment #2 from Daniel Santos <daniel.san...@pobox.com> --- So I believe this is happening because the file is in a subdirectory that is filtered: [Filters][64] inclusive=0 pattern=/drivers/staging targets=2 Some may call this a user error, but I can't afford to have the entire kernel parsed, but if I need to open a file in my filter, I can't have it mis-parsed. So for the sake of parse jobs, can we modify findProjectFileItem() so that if project->filesForPath(url) fails to find a match, we can still look for a project who's root contains the path of the file? This would solve my problem without forcing me to parse the entire kernel -- since that usually results in KDevelop crashing anyway. -- You are receiving this mail because: You are watching all bug changes.
