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 635242 - Use GtkExpander for message headers
Use GtkExpander for message headers
Status: RESOLVED DUPLICATE of bug 303653
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-11-19 06:35 UTC by Ryan Li
Modified: 2012-11-06 17:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description Ryan Li 2010-11-19 06:35:23 UTC
Currently Evolution uses "show" versus "don't show" in message header preferences. However, this is very much restricted. For instance, in most cases I would only like to see only two headers: From, Subject. While other entries, like Reply-To and Newsgroup, etc. are needed for special messages (e.g. the ones I want to reply to).
The current situation poses a dilemma: If I show all of them by default, they will simply clutter up my screen providing information I don't want at the same time; on the other hand, if they are not shown, to view the extra headers for special messages, I need to set the preference in a time-consuming manner.

Thus I think adding a GtkExpander would be a very nice solution for this. By default it just shows concentrated information of the core information, and after expanding the user-preferred headers will all be shown.

This could be implemented with ease, I just hope it's a good idea for many end users, since I just switched from Thunderbird to Evolution and I noticed some shortcomings in usability like this.
Comment 1 Milan Crha 2012-11-06 17:43:26 UTC
Thanks for a bug report. This had been fixed for 3.1.1, thus for 3.2.0 of stable release, within bug #303653, thus I'm closing this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 303653 ***