https://bugs.kde.org/show_bug.cgi?id=374798
--- Comment #5 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #4) > > Right click on a URL, select 'Save link as', which opens a save-file dialog > > window that lets me choose where I want to save the file. > > That was sort of obvious :), but I wonder what do you want/use this for. > What's wrong with a roundtrip through your browser? Click a link -> your > browser asks you what to do -> the browser performs the required work. OK, I didn't understand before what you had in mind when you asked how I use this feature in other MUA. 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. > As an anecdotal data point about my specific usage patterns: when a link > refers to something which is not a web page, it's very often something > which requires authentication anyway. Trojita won't know what to do in that > case. I don't see that many examples of this in my workflow, but wouldn't it be possible for Trojita to time out in such cases and report something like 'Unable to access'? I don't know how Trojita handles HTML content in messages, but the fact that it's capable of displaying it properly rendered means that it must be capable of downloading arbitrary stuff from the Internet, or not? > We also do not want to deal with showing a progress GUI of possibly N > concurrent downloads, to track their state, to make this list persistent > and to recover from OS/session restarts, etc. In short, as Thomas said, > Trojita is not a download manager. That's a good point, but couldn't this be hidden, for example, behind the systray icon? And I don't mean progress bars or something like that. Just a note that Trojita is trying to access so and so. Just an idea. -- You are receiving this mail because: You are watching all bug changes.
