Bug 21300 - Focus moves backwards in mail list in inbox or other folders when an email is deleted
Summary: Focus moves backwards in mail list in inbox or other folders when an email is...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Julien Moragny
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-20 09:04 CEST by Margot Lawrence
Modified: 2017-08-20 22:06 CEST (History)
1 user (show)

See Also:
Source RPM: claws-mail-3.15.0-4.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Margot Lawrence 2017-07-20 09:04:10 CEST
Description of problem:
My inbox & other mail folders are always sorted threaded & ascending, so the newest messages are at the bottom of the displayed list. Since upgrading to Mageia 6, focus behaviour has changed - when a message is deleted, focus now moves in the wrong direction, backwards to the previous mail instead of forwards to the next. 
For example, if I have two threads in the folder (1 & 2) and each thread has five messages (a, b, c, d, e), if I delete message 2a I would expect focus to move forwards to message 2b, but it now moves backwards to 1e.
And the problem is the same for unthreaded messages - if I delete message 5, focus moves backwards to message 4 instead of forwards to message 6.

Version-Release number of selected component (if applicable):
claws-mail-3.15.0-4.mga6

How reproducible:
Every time I delete an email

Steps to Reproduce:
1. Delete an email (read or unread - problem occurs with both)
2. Focus moves to the previous (i.e. older) message instead of to the next (i.e. newer) message.
Comment 1 Marja Van Waes 2017-07-21 21:06:37 CEST
Assigning to the registered maintainer of claws-mail.

Assignee: bugsquad => julien.moragny
CC: (none) => marja11

Comment 2 Julien Moragny 2017-07-21 22:55:23 CEST
Hi,

You may want to play with the hidden pref next_on_delete (introduced in 3.13.1) :

* A hidden pref has been added, 'next_on_delete'. This controls the
  message selection when a message is deleted. A setting of '0'
  which cause the previous, older message to be selected, a setting
  of '1' will cause the next, newer message to be selected.


the pref is in file clawsrc under /home/user/.claws-mail

regards
Julien
Comment 3 Julien Moragny 2017-07-21 23:01:16 CEST
To complete my previous answer, it's a change of behavior circa mid-2016.

See : 
http://www.claws-mail.org/manual/claws-mail-manual.html#adv_hidden (search next_on_delete)

and (for example)
http://lists.claws-mail.org/pipermail/users/2016-August/017080.html
http://lists.claws-mail.org/pipermail/users/2016-August/017097.html

regards
julien
Comment 4 Rémi Verschelde 2017-07-24 11:39:52 CEST
Duplicate of bug 21290 btw. Might be worth adding a mention to it in the release notes?
Comment 5 Margot Lawrence 2017-07-25 12:27:28 CEST
(In reply to Julien Moragny from comment #2)
> Hi,
> 
> You may want to play with the hidden pref next_on_delete (introduced in
> 3.13.1) :
> 
> * A hidden pref has been added, 'next_on_delete'. This controls the
>   message selection when a message is deleted. A setting of '0'
>   which cause the previous, older message to be selected, a setting
>   of '1' will cause the next, newer message to be selected.
> 
> 
> the pref is in file clawsrc under /home/user/.claws-mail
> 
> regards
> Julien

Thank you. I have found the offending setting and changed it, and claws is now behaving the way that a user would expect.

What a shame that the default is set to the non-useful option - I fear that new users will find this default very offputting and will simply abandon claws without checking for strange defaults in hidden settings.
Comment 6 Julien Moragny 2017-08-20 12:25:59 CEST
(In reply to Rémi Verschelde from comment #4)
> Duplicate of bug 21290 btw. Might be worth adding a mention to it in the
> release notes?

Seems a good idea, is there a specific policy for editing releases notes? (anyway, I can't do it directly at the moment, can't log in the wiki due to bug 20813 )
Comment 7 Julien Moragny 2017-08-20 22:06:49 CEST
The releases notes have been updated. Closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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