Version: 3.3 (using KDE KDE 3.3.0) Installed from: SuSE RPMs OS: Linux I have some data in another partitions (due to space reasons and for sharing with other operation systems). I have symbolic links to this directories. If I start a search within konqueror (extras/search for files) this directories are not searched, and there is no option to allow this.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
no change -- the dialog has some options, but no options is about symlinks
back to REPORTED
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!
Still happens here. Operating System: EndeavourOS KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 kfind 22.08.3
When searching with konqueror symbolic links to directories are not followed. The dialog box has same options, but nothing about symbolic links. Btw: when searching within dolphin there is no way to specify if symbolic links should be followed -- which seems to be he default. So there are two kde tools, two different behaviors -- no option to change. The find command has at least -H, -L and -P ...
I am wondering if this is the actual intended behaviour by the developers. Let's say we have "Drive A" and "Drive B". Drive A contains a symbolic link to "myfile.txt" that is stored in "Drive B". If the user uses KFind to search into Drive A for "*.txt" what is the expected result? I expect that "myfile.txt" should *not* be returned, and rightly so as it is located in a different drive so it is out of scope for the user's search. If the user decides to search for "*.txt" inside Drive B then the file should be returned. Maybe I am not understanding the problem correctly. Please clarify.
Made an account to chip in. Version 24.08.0 is still affected by this issue. (Side note, the copyright notice still reads as 1998-2021 - this seems a little outdated 😛) As suggested, the cleanest solution would be a checkbox that enables following symbolic links within the specified location. We already have two options for case sensitive/include binary files, so it wouldn't stand out in terms of UI design. As for the implementation, I'd be plenty happy if I could just find the files in my symlinked folders - even without deduplication or anything fancy to go along with it. Though I could see it becoming necessary even for a first implementation, as it would have to catch the edge case of symlinked loops (folder A contains a folder. B, which points back to A or to a folder above it).