On 2011-03-16 00:34 , Godfrey DiGiorgi wrote:
On Tue, Mar 15, 2011 at 8:33 PM, steve harley<[email protected]>  wrote:
that's not a hierarchy, it's just a bunch, and a bunch that's sorted by
time, instead of which messages replied to which; it's not really nested at
all because the first item is a psuedo-item that changes depending which
messages are marked read

Mail isn't naturally multi-threaded. It's not a discussion, it's a timeline.

of course it is a discussion, and the timeline approach fails as the discussion branches

a beauty of email is that the discussion need not be linear -- it's not a strict analog of a verbal discussion; people intuitively know this; they go off on pun romps while others are answering the serious question in a thread or getting political, and the timelines of these branches overlap, but a proper display sorts it all out and helps the reader follow the branching, decide what to read and when; for example i just bailed out of the "twicification" and "hamburger" branches of the SMC 15 thread


no, it marks a message when it has been _displayed_; this makes it awkward
to glance at a message body before deciding whether to read it now

Oh, you want it to display a content preview. Just use the web client
for Mail instead.

no i don't want that -- it was just one example of how touching a message is not the same as reading it; there are several practical implications and also a principle at work here


It works fine for me. But that's why they make so many flavors of ice
cream too. :-)

i'll resist the standard "Apple makes only one flavor" reply and ask is an email client a flavor of ice cream, or is it an ice cream shop, or what? how about if food had a preferences menu item, and if you didn't like something about it you could change it as you ate it -- too salty, dial it down / needs more chocolate chips ...

--
PDML Pentax-Discuss Mail List
[email protected]
http://pdml.net/mailman/listinfo/pdml_pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Reply via email to