Bug 358312

Summary:	The shortcut "M" does not move messages
Product:	[Applications] kmail2	Reporter:	Rigo Wenning <rigo>
Component:	commands and actions	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	henrikau, montel
Priority:	NOR
Version:	5.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Rigo Wenning 2016-01-21 14:42:37 UTC

Moving messages with the keyboard does not work. The shortcut "M" calls the dialog. One can select the folder. On carriage return, the dialog window disappears. In 4.14 the messages disappeared. Now nothing happens. If one uses drag & drop it works. The message is then moved correctly

Reproducible: Always

Steps to Reproduce:
1.Hit key m
2.select folder 
3.hit carriage return

Actual Results:  
dialog disappears, messages are not moved but remain untouched

Expected Results:  
messages should be moved to the destination folder

Moving messages via drag & drop of messages to target folder works

Comment 1 Rigo Wenning 2016-01-21 14:44:29 UTC

Shift-Delete works and "move to trash" via "del-key" works too

Comment 2 Henri K 2016-01-21 16:23:03 UTC

Works for me. Using kmail5-15.12.0-1.2.x86_64, openSUSE TW, Plasma 5.5.2, Qt 5.5.1.

Comment 3 Laurent Montel 2016-01-21 17:52:10 UTC

it works fine here.
Is it imap account ? pop 3 accout ?

Comment 4 Rigo Wenning 2016-01-21 18:58:27 UTC

Problem is that the default is now on "Cancel". So typing the folder, arrow, carriage return was very quick. So quick after 10 years of usage that I did not realise that the default moved from "OK" to "Cancel" to move messages, I now need 3 keystrokes more or doing alt-O, which is really inconvenient. But this is not really a bug. Somebody just decided against a setup that had high usability advantages for me.

Comment 5 Laurent Montel 2016-01-22 07:23:30 UTC

nope default is on "ok"...

Comment 6 Rigo Wenning 2016-01-22 09:21:48 UTC

The bug appeared after upgrade to KF5. Now I have rebooted the machine (not only logged out/in again) and the default is on "ok" now. I should have taken a screenshot. But maybe this bug report serves others who run into the same issue. For me, it is solved.