Bug 488186 - per-action customisable menu and history when opening URIs, files and other MIME associations
Summary: per-action customisable menu and history when opening URIs, files and other M...
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Other All
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
Depends on:
Reported: 2024-06-07 23:18 UTC by Paul Wise
Modified: 2024-06-10 19:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Note You need to log in before you can comment on or make changes to this bug.
Description Paul Wise 2024-06-07 23:18:43 UTC
Similarly to the clipboard actions functionality:

I would like to be able to choose which app to open every time I open a URI, file or other MIME type from an app that doesn't already handle it.

I would also like to be able to customise the list of actions and add my own actions with custom commands.

I would also like a tray icon with history of the URLs/files/etc opened so I can search and browse them.

This would be useful when trying out new applications, when I have lost a URL, when I need to stash URLs in a file instead of opening them and many other situations.

In terms of the UI, probably the history functionality and system tray item should be associated with "Recent files/URLs". The new MIME action functionality could update the "File Associations" config (and also be available there). I guess the open menu could be called the "File actions menu" or similar.
Comment 1 Nate Graham 2024-06-10 19:31:53 UTC
Thanks for sharing this idea!

As expressed, I think it's too big to fit in a bug report. This would be a major system feature requiring hundreds or thousands of hours of engineering effort to build, QA, and ultimately maintain over time. Such a thing would require substantial discussion and developer buy-in.

I'm also not sure how generally useful the proposed feature would be. I could see the annoyance factor being very high for people with a more typical workflow and set of expectations for opening things.

As such, I think we're going to have to say "thanks but no thanks" to this one, sorry!