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 346408 - "Show matching articles' Threads" not working
"Show matching articles' Threads" not working
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other Linux
: Normal normal
: 1.0
Assigned To: Charles Kerr
Pan QA Team
: 338726 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-02 18:41 UTC by dcb
Modified: 2006-07-06 07:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description dcb 2006-07-02 18:41:34 UTC
Article threading isn't working the same now as in old-Pan.  Since they say "a picture is worth a thousand words," I'll display the problem with screenshots.

Here's a snap of old Pan with "Show Matching Articles/Match Unread Articles":

http://doug.freeshell.org/files/pan1.png

And the same "Show Matching Articles/Match Unread Articles" in new Pan.

http://doug.freeshell.org/files/pan.png

It's exactly the same, which is fine.  However, article threading is very untidy this way, which is why I don't use that view very much.  The fix, however, is to use "Show Matching Articles' Threads/Match Unread Articles".  Now the header display looks much cleaner in old Pan:

http://doug.freeshell.org/files/pan3.png

However, in new Pan, selecting "Show Matching Articles/Match Unread Articles" in the menu doesn't change the header Pane threads at all.  The screenshot would be exactly the same as "pan.png" above.

If it's not an outright bug, I think old Pan's "Show matching articles' Threads" feature was much nicer.
Comment 1 Charles Kerr 2006-07-03 16:20:46 UTC
It's an outright bug.
Comment 2 Charles Kerr 2006-07-06 03:12:02 UTC
Fixed for 0.103.
Comment 3 Charles Kerr 2006-07-06 07:26:42 UTC
*** Bug 338726 has been marked as a duplicate of this bug. ***