Bug 3840 - Actions do not honour next_on_delete
Summary: Actions do not honour next_on_delete
Status: NEW
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Message List (show other bugs)
Version: 3.14.1
Hardware: PC Linux
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2017-06-22 20:02 UTC by Tristan Miller
Modified: 2018-05-01 10:11 UTC (History)
1 user (show)

See Also:


Attachments

Description Tristan Miller 2017-06-22 20:02:47 UTC
When the next_on_delete preference is set to 0, the previous message is supposed to be selected when the current message is moved, deleted, or trashed.  This works fine when a message is moved, deleted, or trashed using the mouse, the pull-down menus, or the keyboard shortcuts.  However, it doesn't work when invoking an action that causes the message to be moved (or maybe also deleted or trashed).  Invoking such an action always causes the selection to advance to the next unread message.

Steps to reproduce:
0. In clawsrc, set "next_on_delete" to 0
1. Go to Configuration -> Actions
2. Add a new filter action whose only rule is to move the message to a given folder.
3. If desired, set a keyboard shortcut for the action.
4. Go to any folder with a run of unread messages, followed by one or more unread messages.
5. Select any of the unread messages except for the last one
6. Invoke the action via the Tools->Actions menu or via the keyboard shortcut.

Observed behaviour:
7. The message gets moved to the folder specified in Step 2, and the next unread message in the current folder gets selected.

Expected behaviour:
7. The message should get moved to the folder specified in Step 2, and the previous message in the current folder should get selected.
Comment 1 Tristan Miller 2017-06-22 20:10:07 UTC
Oops, there's a typo in my steps to reproduce.  Steps 4 and 5 should read as follows:

4. Go to any folder with a run of read messages, followed by one or more unread messages.
5. Select any of the read messages except for the last one
Comment 2 Ricardo Mones 2018-04-30 19:01:13 UTC
This bug seems very similar to #1857.

Note You need to log in before you can comment on or make changes to this bug.