https://bugs.kde.org/show_bug.cgi?id=374798
--- Comment #7 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #6) > (In reply to Robert Kratky from comment #5) > > The problem with the round trip through the browser is that I have my > > desktop environment configured in a way that only a certain limited subset > > of MIME types is opened through the browser when I click on them. For > > example, I use an image viewer to open images by default. So, when I click > > on a URL that points to an image in Trojita, the file is opened by the image > > viewer. > > > > Now, that particular helper app that's used to open a specific type of file > > may or may not have the functionality to save that file to a disk (for > > example, my GIF viewer isn't capable of doing that). So, I'm stuck with two > > options: > > > > * copy the URL from Trojita and use wget or similar > > * copy the URL from Trojita and open in a browser > > > > Both are possible but both are annoying and the 'round trip' has gotten a > > lot more complicated than just clicking on a link. > > The DE that I use (Plasma) has a switch which controls whether an URL is > always opened in a web browser, or whether the MIME type is guessed/checked > (I don't actually know, maybe it uses its generic network stack to download > or HTTP HEAD it first) and then an appropriate local application is used for > its handling. Perhaps you can use a similar feature as well? I use Plasma, too, but I actually like to open the individual types of files in their associated apps. Even from Trojita. But I'd like to have the opportunity to download the file instead of opening it when I choose so. Even if I decided that I only want to open the files from Trojita in a browser, it's not possible. (Unless I'm mistaken, there'no way to configure this behaviour on a per-app basis.) > I believe that it's the job of the "rest of the desktop environment" to > provide a wrapper which gets triggered when a user "just clicked a web link" > to ask what they intend to do. I don't want to manage filetype associations > within Trojita, either; these are bits which we simply delegate to the DE. That sounds reasonable, but I don't know of any DE that would implement this. Perhaps it would be possible to implement custom menu items as Thomas suggested? I'd gladly write a wrapper script myself then. -- You are receiving this mail because: You are watching all bug changes.
