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

Méven <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kio/-/commit/7b29ffa
                   |                            |2aa1e0486c323eed496cb891f61
                   |                            |3501cc
             Status|ASSIGNED                    |RESOLVED

--- Comment #21 from Méven <[email protected]> ---
Git commit 7b29ffa2aa1e0486c323eed496cb891f613501cc by Méven Car.
Committed on 11/09/2026 at 07:13.
Pushed by meven into branch 'master'.

kdirlister: keep entries that share a name but not a url

A search for a file name found one hit of each name. An icon theme searched for
document-save gave 8
files where the folders hold 28, and a folder holding testfile.txt beside
AppData/testfile.txt and
Documents/testfile.txt gave one of the three.

A listing skips an entry it has already seen in the same pass, and it knew an
entry by its name. The
folder a search result is listed in gives every entry a url of its own, and
several of those entries
carry one name, so every hit after the first read as a repeat of it. An entry
is now known by that
url where it carries one, and by its name where it does not, since the name is
the whole of what
differs between the children of one directory. The two are asked per entry
rather than per listing,
because one listing can hold both: a search folder gives its own "." entry no
url.

Regressed in ee2b19bbdaadc279d7f6251ca347b84f701823b5.

M  +68   -0    autotests/kdirlistertest.cpp
M  +1    -0    autotests/kdirlistertest.h
M  +15   -6    src/core/kcoredirlister.cpp

https://invent.kde.org/frameworks/kio/-/commit/7b29ffa2aa1e0486c323eed496cb891f613501cc

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

Reply via email to