Re: possible new sort option

andré via balsa-list <[email protected]>
Newsgroups gmane.comp.gnome.apps.balsa
Message-ID <[email protected]>
Hi Peter,

Le 2018-08-19 à 19:02, Peter Bloomfield a écrit :
> A new branch 'threading' has been added to Balsa's GitLab site[0]. It 
> currently has the first part of a proposed change to Balsa's message 
> threading.
> 
> The three radio buttons on the 'View' menu have been replaced with a 
> simple 'Thread messages' check-box, and checking it enables a modified 
> JWZ threading algorithm which constructs threads only by message-id, 
> ignoring the subject header.
> 
> At present there is no user interface to request full JWZ threading, 
> although the code for it still exists. It doesn't belong on the 'View' 
> menu. It should be a per-mailbox option, not global, so it doesn't 
> belong in the 'Preferences' dialog. That leaves the mailbox 'Properties' 
> dialog, so the next step is to add a check-box there. Threading is also 
> a per-mailbox option, but not currently shown on the 'Properties' 
> dialog, so perhaps we should add two check-boxes:
> 
> [ ] Thread messages
> [ ] … by subject as well as by references
> 
> with the second grayed out if the first is not checked. Opinions?

Sounds great
... except maybe a little better if the second check box said
"by subject if no reference" ?
Or am I misunderstanding something ?

> 
> Oh, by the way: this message *looks like* a reply to my earlier post, 
> but is actually a fresh post, with no 'References' header. JWZ threading 
> will place it in the earlier thread, because of the subject, but the 
> Balsa built from the 'threading' branch will make it the head of a new 
> thread. Happy testing!
> 
> [0] https://gitlab.gnome.org/GNOME/balsa
> 

>>
>> Peter
> 

-- 
André
_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.