GNOME Bugzilla – Bug 218571
All threads collapsed or expanded defined in user configuration
Last modified: 2021-05-19 11:08:54 UTC
A feature that allows the user to configure wether Evolution shows all threads collapsed or expanded on startup. As it is, Evolution shows threads in which new messages have arrived expanded. Maybe a "Don't expanded threads with new messages" option would suffice, those threads that the user has manually expanded in a previous session should still be expanded on startup.
depends on 18570; still in 2.1.4
*** bug 239366 has been marked as a duplicate of this bug. ***
Apologies for any spam... cc'ing usability-maint on all Evolution usability bugs. Filter on EVO-USABILITY-SPAM to ignore.
changing wrong dependency
Bumping version to a stable release.
Hey :) I'm not sure whether I got your request correctly. Could you rephrase your issue? FWIW: Currently, Evolution saves the state of the expanded/collapsed mail.
Here threads are expanded after a search, so evolution doesn't save the state at any time. Hence an option that keeps threads collapsed generally would be very nice.
Hm. Thanks for the feedback. Can you provide detailed steps to reproduce? Which version are you using?
I'm using evolution 2.28.2, compiled on gentoo. This is reproducible by selecting a folder (IMAP backed in my case), collapsing all threads and then issuing a search (on current folder). Search finds some elements (doesn't matter if they're part of a thread). If you now clear the search field and thus clear the results, all threads are expanded. As a side note: Evolution also forgets to collapse the threads after a restart, shouldn't this setting be remembered?
Thanks henry, i can reproduce the bug against master (2.29.91) with the steps given in comment#9
*** Bug 615053 has been marked as a duplicate of this bug. ***
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.