[Users] [Bug 3600] New: next_on_delete doesn't work if sorted descending

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Fri Jan 22 21:36:36 CET 2016


            Bug ID: 3600
           Summary: next_on_delete doesn't work if sorted descending
    Classification: Unclassified
           Product: Claws Mail
           Version: 3.13.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: UI/Message List
          Assignee: users at lists.claws-mail.org
          Reporter: barry at python.org

I just updated Ubuntu's claws-mail to 3.13.1 and have noticed the change in
behavior controlled by next_on_delete.  I know there is a hidden variable that
controls this, but unfortunately it appears not to work correctly when (I
think) sort is descending.

Specifics: I sort on the message # column, and the little arrow points up,
which I believe is sort descending.  IOW, the newest message (i.e. the one with
the highest message #) is at the top of the message list.  Now I hit 'd' to
delete the message.  The selected message does not change - it stays with the
selected and newly deleted message.  Note that I also do *not* have "Execute
immediately when moving or deleting messages" selected, so the newly deleted
message just gets a blue < icon next to it.

This happens regardless of whether I set next_on_delete to 0 or 1.

Note though, that if I swap the sort order to ascending (i.e. the little arrow
points down), then things appear to work as intended.

You are receiving this mail because:
You are the assignee for the bug.

More information about the Users mailing list