| Summary: | "Locate current document in project" button in project view not working | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Frank Souza <franksouza183> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | |
| Priority: | NOR | ||
| Version First Reported In: | 5.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Frank Souza
2017-04-04 00:03:56 UTC
This works for me in 5.1.0. Single or multiple projects, tree folded or not, don't make a difference. Same here. Needs more info. FWIW, I'm also using the Arch packages, so exactly the same build... Sorry for the lack of information. I did some more tests and only then realized that this problem occurs only in .php files, for other files this seems to work. PHP files still work for me (using them daily). Is there anything else that might make your PHP files different from the others? Different filesystem/user/permissions? Does it work for non-PHP files in exactly the same dir with the same permissions? I assume you've checked that your affected files are actually *in* the project...(even if they're in the same tree, you could have a rule to exclude them). I've figure it out: symbolic links. The major part of my php files are sym links from a base project. Now I don't know if this a bug or expected. That's why I'll not mark as resolved until someone confirm. Thanks everyone! Reproducible here. KDevelop seems to normalize the path - the titlebar shows the target of the symlink, and 'find in project' works after opening a symlink if the target is in the project (whether or not the symlink was). Not sure what the ideal behaviour would be; currently it's inconvenient for your case, but keeping symlinks separate might cause problems with permissions, opening the same file twice, etc. the lookup feature could (and should) use the indexed string of the normalized path to find the corresponding project item, this should fix this issue then, I guess - patches welcome! Taking into account the concept of symbolic link, this is something that must be fixed since this break its purpose Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |