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

            Bug ID: 408813
           Summary: Provide option to not prefix file:// when copying
           Product: frameworks-kio
           Version: 5.44.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: fa...@kde.org
          Reporter: samj...@gmail.com
                CC: kdelibs-b...@kde.org
  Target Milestone: ---

I have seen bug #241225 which already requested this and was rejected. However
that was against KDE 4 so re-filing against KDE 5.

I have been using KDE ever since my very first Linux days (it was KDE 3 then)
and I have sort of gotten used to the irritation of having to manually delete
the initial file:// prefix whenever I copy-paste a file path from a KDE
application to terminals, GTK file dialogs or text boxes.

However this needn't be so. As seen in the other bug, it has the potential to
lose KDE users. I am sticking with KDE because of its more numerous advantages,
but I hope all these needless irritations can be polished away to be more
friendly and useful.

If I am living near Salem, Tamil Nadu, India and there is a Salem, Oregon, USA
(which most people here don't know), the Salem I refer to will almost always be
the town here and not the one in the USA. Similarly the path I refer to by a
plain path without protocol prefix will be my local file system only. There is
no need for always prefixing file:// and having the user delete it when it
creates a problem.

Even in web browsers, typing gmail.com and pressing enter automatically
prefixes http:// since that is the most common protocol. Why should the local
behaviour be any different?

The technology should serve the convenience of the user, and the user shouldn't
have to adjust to the technology.

If it can be fixed for one particular case: bug #170608 why can't it be fixed
in  general?

Thanks!

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

Reply via email to