https://bugs.kde.org/show_bug.cgi?id=358221
Bug ID: 358221
Summary: Tilde/variable expansion is treated differently than
the equivalent path
Product: krunner
Version: 5.5.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: general
Assignee: m...@vhanda.in
Reporter: k...@happyjack.org
When tilde/variable expansion is used in krunner, suggested completions are
different than if the complete path had been used.
Example: I open krunner and type:
~/foobar
or
$HOME/foobar
Where $HOME/foobar is a directory. The result is that a lot of documents are
returned in the search dropdown, followed by the Locations area, which has “Go
to file:///home/me/foobar”.
However, if instead I enter:
/home/me/foobar
Just the Locations area shows up and it directly says “Open /home/me/foobar”.
The biggest problem with this is that if I type “~/foobar” and hit enter, it
opens whatever document happens to be at the top of the list, whereas my
expected behavior is that it opens the directory, since I specified it exactly.
Essentially, since ~/foo and /home/me/foo are the same thing, they should be
treated identically.
Reproducible: Always
Steps to Reproduce:
1. Hit Alt-F2 to open the krunner dialog
2. Enter a valid path to a file in your home directory, using ~ to represent
your home directory
Actual Results:
If the search string matches documents, they are listed first, meaning you have
to navigate down to the Locations area to open the file/directory.
Expected Results:
If a path to an existing file is specified, that is the first entry in the list
so hitting enter causes the file to be opened.
--
You are receiving this mail because:
You are watching all bug changes.
