After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794832 - Option to close window on deletion, not open next mail
Option to close window on deletion, not open next mail
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 220999 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2018-03-30 08:53 UTC by Anders
Modified: 2018-07-27 08:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Anders 2018-03-30 08:53:14 UTC 
If you open a mail in a separate window and press the "delete" button. Evolution automatically opens the next mail in the same folder, marking it read depending on the settings.

The behavior I want is to close the active windows upon deletion.

Is this achievable ?
Comment 1 Milan Crha 2018-04-03 13:48:32 UTC 
Thanks for a bug report. This cannot be done at the moment. There can be set to move to the previous message after the current message is deleted or marked as Junk in new enough Evolution, but there is no option to close the window after the shown message is deleted or marked as Junk. I think the option would make sense, even if it's just a hidden option with the default to keep the current behaviour.
Comment 2 Milan Crha 2018-04-03 15:12:22 UTC 
I made it a hidden option. Once you've the version which contains the fix run from a terminal:

  $ gsettings set org.gnome.evolution.mail browser-close-on-delete-or-junk true

and since then the message browser window will close instead of move to the next (or the previous) message.

Created commit ed93c95b28 in evo master (3.29.1+)
Comment 3 Anders 2018-04-04 06:54:13 UTC 
That's great. Thanks
Comment 4 Milan Crha 2018-07-26 17:18:56 UTC 
*** Bug 220999 has been marked as a duplicate of this bug. ***