Re: Ordering of "threaded by subject" messages

Chris G <[email protected]> Mon, 19 Oct 2009 11:18:09 +0100
Newsgroups gmane.network.tin.user
Message-ID <20091019101809.GG15705@chris>
On Mon, Oct 19, 2009 at 11:59:54AM +0200, Urs Janßen wrote:
> In <20091019092141.GD15705@chris>, Chris G wrote:
> > I read a newsgroup where the messages are gatewayed from both a web
> > forum and a mailing list. Thus, while some threads have proper
> > References: in the headers joining them, up other threads don't and tin
> > just does its best on the basis of the Subject: being the same.
> > 
> > I'd like the non-References threads to be sorted by date rather than
> > the (apparently) random order they appear in at the moment.
> > 
> > So I assumed I needed to set sort_threads_type=4 in my tinrc.  But it
> 
> this will sort the order in which the threads appear, not the order
> of the articles inside the thread.
> 
Ah, that explains why it appeared to do nothing!  :-)

> > doesn't seem to work, I still get an apparently random order when
> > viewing a thread which doesn't have any References:.
> 
> sort_article_type=6
> but threaded messages will always stick together
> 
I already have sort_article_type=6.

I realise that threaded messages will always stick together, that's
absolutely fine and as I would expect.  

What I want is to be able to set the order in which the messages
within the thread are displayed when there are no References:.  I.e. 
when I hit 'l' to expand the thread or when I TAB through messages in
the thread I want them to be displayed in [ascending] date order.  As
it is at present they appear to be displayed in an entirely random
order.


> > I have done "rtin -u" but it didn't seem to change anything.  This
> > *should* do what I want shouldn't it?
> 
> no, "-u" will rebuild the cached overview data which is used for
> thrading but the threading is always done at runtime.
> 
OK, I suspected that might be the case but wasn't quite sure.

-- 
Chris Green