TODO LIST FOR T-PROT ==================== For more issues and/or some details, please see the BUGS section of the man page. To report bugs, please first see the BUGS file. To make suggestions or tell about features you miss, please drop an email to . Known Bugs (more severe ones come first) ======================================== * In raw multipart messages we snip MS-like TOFU even if there is no relevant text above -- we will have to detect Boundaries and Content-Type lines as for "$mua eq mutt" in t-prot, l.1142. Wishlist ======== * Better heuristics for M$ style TOFU. The actual algorithm still is just too greedy (actually, it simply snips most things down to the signature). User ignorance makes it tricky to detect gold inside the crap, though. As always, comments and ideas are welcome. * New option to block-align lines of text. Should be especially pleasing when used together with -k (you could re-align a whole para- graph using these both). Rejected issues =============== * If you set mutt's display_filter to "tee foo" when viewing a pgp signed message and attach the resulting file to a pgp signed message, the result is confusion when displaying this new message with t-prot. This sounds much like "garbage in, garbage out", so just keep in mind that the whole idea behind t-prot using the display_filter thing is that you can turn it off with just one key stroke. It is definitely not t-prot's responsibility to make *everything* look good and readable. Known Bugs for t-prot.sl (more severe ones come first) ====================================================== * Mailing list footers seem not always to be snipped correctly from MIME/multipart messages if called by t-prot.sl. Wishlist for t-prot.sl ====================== Known problems: * t-prot.sl interacts badly with some other macros using the read_article_hook. * ESC-0/ESC-1 as described in t-prot.sl does not take effect on the article currently displayed (just on those processed later on). Please remember that t-prot.sl is an *example* script (for you to get an idea on how to integrate t-prot into other software), so these are really low priority. However, patches in unified diff format are always welcome. ;)