https://bugs.kde.org/show_bug.cgi?id=353883
Loucura <loucur...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |loucur...@gmail.com
--- Comment #2 from Loucura <loucur...@gmail.com> ---
I was going to report a new bug, but this one seems close enough to what I
found.
Testing with the latest KDE Neon (happens with older versions as well).
It seems errors only happen when entering a relative path that has a dot
somewhere.
Without dots, it works fine.
Absolute paths work fine too.
Absolute paths:
/home/neon/Documents -> fine
/home/neon/.local -> fine
Relative paths (inside ~):
Documents -> fine
.config -> Invalid protocol
.local/share -> Invalid protocol
Test.Folder -> Dolphin does not support web pages (tries https protocol)
Relative paths (inside /home):
neon/Documents -> fine
neon/.config -> Dolphin does not support web pages (tries https protocol)
So, I guess that when the path starts with '/', Dolphin knows it's a file path.
But, when it doesn't start with '/' (or a protocol scheme like "ssh://") but
the path includes a dot, it thinks it's not a folder path, and may even think
it's a web URL.
The location bar in Dolphin correctly autocompletes relative paths, though.
Maybe when the path doesn't start with '/' and doesn't include "://" somewhere,
the system should check if a file/folder with that relative path exists and:
- If it exists -> open that file/folder;
- If it doesn't exist -> proceed to do what it does currently.
Or something like that.
Maybe the title of this issue should be updated. (I would, but I don't know if
I should).
--
You are receiving this mail because:
You are watching all bug changes.
