I was thinking about this too, but then had second thoughts about it. A typical e-mail client has 3 windows: one is the tree of mailboxes, which would easily map to the Leo tree. Another is the message text, which would map to the node body. There is at least one more window in the mail client: a table with subject, date, etc, one line for each message. This may be the tricky part. Leo could probably deal well with the attachments.
For searching, Thunderbird is doing a fine job. The main advantage would be to deal with emails just like with other files. So far all the email data lives in a separate world. This has become a common design strategy though: much data is bound to the program producing it, although it would be much nicer to keep data on a per project or topic basis together, not on a per-tool basis. Josef -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
