[rfe][search view] the displayed numbers of mails in a thread don't align upon differing arity about alot HOT 5 CLOSED

I'm not sure what you mean here. instead of

timestamp (1) subject
timestamp (15) subject

you would like to see

timestamp  (1) subject
timestamp (15) subject

?
This sounds really easy to to but is in fact really difficult w/o collumns:
The reason is that for the search to be usable, it only reads the threads that actually get displayed.
so It doesn't know the maximal number of mails contained in its thread. Therefore, you can't
fix the length of the message count to align them nicely: If you chose length 2 and
force it with sth like "%2d" % num, and suddenly a thread with 200 mails gets displayed..
also, setting the length to 4, assuming no thread will contain more than 9999 mails might waste
screenspace in most cases.

Letting the user fix this as a config option? I don't think so: it only shifts responsibility.

from alot.

you would like to see [...]

yes

it only reads the threads that actually get displayed.
so It doesn't know the maximal number of mails contained in its thread. Therefore, you can't
fix the length of the message count to align them nicely
also, setting the length to 4, assuming no thread will contain more than 9999 mails might waste
screenspace in most cases.

yes, I expected something like that

is in fact really difficult w/o collumns

actually, I find the idea of a column based layout more and more appealing. What's ur position on that?
Certainly wouldn't qualify as a small fix, but as a long term goal? U think that's desirable?

Letting the user fix this as a config option? I don't think so: it only shifts responsibility.

<3

from alot.

generally a nice idea. I haven't used a table widget with urwid so far.

from alot.

If I find some time, I'd love to scribble together a very basic stand alone prototype. Won't manage before tuesday at best, so, if u r bored, ... ;)

from alot.

Tuesday 25/08/2011? I'm status you've missed that by a few years now :-)
So since obviously this hasn't been missed I'm closing this issue as wontfix.
cheers

from alot.