Bug 424432 - Autocomplete makes it very hard to navigate folders
Summary: Autocomplete makes it very hard to navigate folders
Status: RESOLVED DUPLICATE of bug 420966
Alias: None
Product: dolphin
Classification: Applications
Component: bars: location (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-19 16:46 UTC by Michał
Modified: 2020-07-20 00:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał 2020-07-19 16:46:49 UTC
SUMMARY
The way autocomplete works have been changed recently (I don't know exactly when, I do updates rarely). Now, when autocomplete suggests something and user presses enter after entering a valid path in Dolphin, it navigates to the autocompleted path, instead of the one that user entered.


STEPS TO REPRODUCE
1. Have folders like this:
/mnt/nas/
/mnt/nas-backup/
(It's possible that Dolphin has to learn the possibilities, so perhaps manual entering both paths is needed as a precondition).

2. In Dolphin, press Ctrl+L to enter the path to go to. Type "/mnt/nas", press Enter.

OBSERVED RESULT
Dolphin goes to /mnt/nas-backup instead of /mnt/nas, because autocomplete have suggested "/mnt/nas-backup".

EXPECTED RESULT
Dolphin navigates to what user entered: /mnt/nas.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Dolphin 20.04.2
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
This kind of autocompletion would be OK, if there was no ambiguity, but in case of one, it should not kick in.
Comment 1 Michał 2020-07-19 16:49:24 UTC
Just to add, adding slash after the entered path doesn't help at all. When I type "/mnt/nas/" Dolphin goes to autosuggested first directory within /mnt/nas, in my case it's "/mnt/nas/ backup".
Comment 2 Nate Graham 2020-07-19 21:57:50 UTC

*** This bug has been marked as a duplicate of bug 420966 ***