Version: 1.8.92 (using KDE KDE 3.4.92) Installed from: SuSE RPMs OS: Linux when I open an attachment in kmail, then the file is opended in a temporary directory. when I edit the attachment and later want to save it, then I have to go to the directory where I want to save the attachment. The other way around I can save the file where it shall be stored, but I have to open konqueror, go to the directory, where I saved the file, and have to open the file again. This is very cumbersome, and as I do this very often, it is very annoying. It would be great, to have a menu point in the right click menu, stating: "save and open", "save and open with...". Then when I click on one of these menu entries, I will be asked to save the file somewhere and afterwards open the saved file instead of some file in a temporary directory. Then after editing i do only click the save button and can close the application. For me this sounds very much easier and intuitive than the both other ways around.
I like the idea (my votes goes here) but the imaginary popup menu would somehow... a bit complicated. Too much. Open, open with, save, save and open, save and open with... Submenus won't solve the problem. Just thinking out loud: read "or" between points a) save after saving opens a pane inside mail with content of the dir -- if you want to open it you click on file, not a attachment b) before open the file is not saved to tmp but to specified dir, so it is possible to edit it, when you try to open attached doc for which exists edited "alter ego" program asks which one to open c) no other idea right now I like (a) :-)
Or, a check box added to the "Save As" and "Save Attachments" dialogs with "Open Containing Folder" or a similar phrase that means "open the folder where I saved the attachment" would save a few clicks.
*** Bug 166531 has been marked as a duplicate of this bug. ***
It is not exactly a duplicate, but the wish is similar. I would suggest that kmail automatically rereads as changed
Sorry, had too much bugs opened and posted the above in the wrong one
*** This bug has been marked as a duplicate of bug 52813 ***