nmh-workers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] exciting new stuff for 2.0


From: Igor Sobrado
Subject: Re: [Nmh-workers] exciting new stuff for 2.0
Date: Thu, 22 Dec 2005 17:38:26 +0100

In message <address@hidden>, Harald Geyer writes:
> 
> >  + we should have a new format string escape sequence to add an ASCII
> >    representation of the thread tree, so you can make scan display
> >    something like this:
> >  441  12/18 Joel Uckelman o     [Nmh-workers] mhshow: invalid QUO
> >  442  12/18 Josh Bressers +o    Re: [Nmh-workers] mhshow: invalid
> >  443  12/18 Paul Fox      +o    Re: [Nmh-workers] mhshow: invalid
> >  444  12/18 Joel Uckelman |+o   Re: [Nmh-workers] mhshow: invalid
> >  448  12/19 To:nmh-worker | +o  Re: [Nmh-workers] mhshow: invalid
> >  447  12/19 To:nmh-worker +o    Re: [Nmh-workers] mhshow: invalid
> 
> Would this really be useful? I think to pick one thread but sort it
> by Date rather than as tree is much more natural for ML discussions.

I think that nmh developers spend too many time sending email to
mailing lists.  ;-)

> How about:
>   441  12/18 Joel Uckelman (0)   [Nmh-workers] mhshow: invalid QUO
>   442  12/18 Josh Bressers (1)   Re: [Nmh-workers] mhshow: invalid
>   443  12/18 Paul Fox      (1)   Re: [Nmh-workers] mhshow: invalid
>   444  12/18 Joel Uckelman (2)   Re: [Nmh-workers] mhshow: invalid
>   448  12/19 To:nmh-worker (3)   Re: [Nmh-workers] mhshow: invalid
>   447  12/19 To:nmh-worker (1)   Re: [Nmh-workers] mhshow: invalid
> 
> This would provide - depending on sorting - the same information as
> above, could be calculated statically/on a per message basis, would be
> easier to represent on a terminal and easier to parse for humans if the
> thread is longer than the screen.

Sounds great, I like this one.  But I hope that the default format
will not change.

Cheers,
Igor.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]