Version: (using KDE 4.1.3) OS: Linux Installed from: Debian testing/unstable Packages Admittedly a minor yet somewhat annyoing bug: It's possible to attach multiple files at once by selecting a range of files in the file attachment dialog using "Shift-click". It's not possible however to select multiple non-consecutive files using Ctrl-clicks. You have to attach these files one at a time and have to re-open the attachment dialog for each of them, which is cumbersome. That's a regression compared to older kMail versions (KDE 3.5 series) where this was possible. Maybe there's just a misdefined flag when opening the dialog window?
It works again in svn trunk revision 896766, it does not shows the (+) and (-) over the files (as dolphin does), but it is possible to select multiple non-consecutive files.
*** Bug 180961 has been marked as a duplicate of this bug. ***
As bug 180961 has been marked as a duplicate of this, I'll repeat what I said in that bug here to bring it all together (as what I'm finding is somewhat different to what's described above. When I try to attach multiple files to an email, <shift>+<click> acts extremely strangely. Because a single click on a file submits the dialogue (itself a bug, I think, so I'll be opening one for that as well) the only way I can attempt to multi-select is to START with <shift>+<click>. The way I EXPECT this to work is that when I select my first file with <shift>+<click>, that file and ONLY that file should be selected. Then when I select a second file with <shift>+<click>, the second file and everything between it and the first should be selected. But instead of this, an apparently random (but consistent) selection of files are selected (see attachment, firstclick.png, which shows what's selected when I <shift>+<click> on "obama.gif")
Created attachment 30384 [details] Result of <shift>+<click> on "obama.gif" when nothing else has been selected.
Created attachment 31404 [details] Crash output
Created attachment 31405 [details] GDB output
Sorry, the two attachments are invalid. I don't know what's going on here, but I attached them after updating a DIFFERENT bug - for some reason the bug tracker put me onto this bug after updating it rather than the one I'd updated.