https://bugs.kde.org/show_bug.cgi?id=425154
David Faure <fa...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |ASSIGNED
--- Comment #3 from David Faure <fa...@kde.org> ---
Thanks for the useful feedback and thought process.
1. There are other inherited mimetypes, many others. See
https://specifications.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-0.18.html
and the sub-class-of attribute in /usr/share/mime/packages/freedesktop.org.xml
The spec for choosing which application to start
(https://specifications.freedesktop.org/mime-apps-spec/mime-apps-spec-latest.html)
does not recommend separating inherited mimetypes from non-inherited ones. In
general I think this would be harmful.
2. sounds useful, assuming it is generalized to all cases of inheritance. If I
remove kate from application/x-desktop, maybe I just want to stop using kate
for desktop files, or maybe I want to stop using kate altogether for all
text/plain files. I see the benefit of asking the user which one is wanted.
3. is the real issue IMHO. When the user says "open .bin files with okteta" and
the system only finds application/octet-stream for that .bin file, then we
should offer creating a new mimetype on the fly for that extension, and only
associating that one with okteta. This would avoid getting into the need for
the other "solutions", which are mostly workaround to this problem.
4. I thought we already did that. But indeed text/x-python is a bit of a
difficult case because of multiple inheritance (it inherits both
application/x-executable and text/plain). And the code was incorrect in case of
multiple inheritance. The fix is up for review at
https://invent.kde.org/frameworks/kservice/-/merge_requests/9
One issue fixed :-)
--
You are receiving this mail because:
You are watching all bug changes.
