[dolphin] [Bug 447119] Summary: Dolphin/Baloo search with symlinks

[Stefan Brüns]

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

--- Comment #17 from Stefan Brüns <stefan.bruens at rwth-aachen.de> ---
(In reply to tagwerk19 from comment #16)
> (In reply to Stefan Brüns from comment #12)
> > Dolphin returns the correct result only when the path of the current directory is its canonical name.
> Meaning that Dolphin should follow any symlinks before doing a search and
> (silently) query baloo with the canonical path? Although I'm not sure
> whether Dolphin should then show the results relative to the symlink or with
> the canonical path.

The "Path" column should display the canonical path. After all, that's where
the file is actually located. (And in case the symlink started on a different
filesystem, also the place where the space is consumed).

This is consistent with how directory sizes are calculated, symlinks are not
followed, otherwise you may count files several times.

> It makes sense ...
> 
>     ... although it implies that the index *only* ever contains canonical
> paths.
> 
> Would also need to be careful that baloosearch and filenamesearch do the
> same thing.
> 
> Edge cases?
> 
>     $ balooshow -x  path-including-symlink

balooshow already handles this correctly, the canonical path is shown in square
brackets (if it differs from the specified path):

> balooshow -x ~/Sources/testdata/symlink_parent/testdata/hello.txt 
> 12ccd4a0000002d 45 19713354 /home/stefan/Sources/testdata/symlink_parent/testdata/hello.txt [/home/stefan/Sources/testdata/hello.txt]

>     $ balooctl index path-including-symlink
>     $ balooctl clear path-including-symlink
> 
> and then evil baloofilerc includes such as
> 
>     folders[$e]=$HOME/Desktop/Documents
> 
> where you've got a symlink on your Desktop to your Documents folder?
> 
> I think the "balooctl index" (and "balooctl clear") does things properly but
> I suspect that the evil include does not...

In case it is not, this should be trivial to fix.

Also, if you break it, you may keep both parts.

-- 
You are receiving this mail because:
You are on the CC list for the bug.