Uwe Brauer <[email protected]> writes: >> Just to get it right: did you look at messages of yours where you had >> replied to someone else and quoted parts of his text? > > Yes! But what are we talking about? The fact that I use, in some > mail, supercite and may use the prefix " >" or even " tassilo>" > > Or html mails?
We are talking about HTML emails where a MUA like thunderbird/seamonkey might use, e.g., HTML divs and CSS in order to differentiate quoted text (on multiple layers) from the text you enter as response. Some super-cool MUAs might even embed JavaScript in order to make mails "interactive" in some respect. So depending on what the MUA does, it might require a full-blown browser at the other end in order to render the mail correctly. >>> mm-text-html-renderer 'w3m > >> I guess that's the main difference. I use the default value which is >> `shr' nowadays, i.e., the builtin elisp HTML rendered which doesn't >> fail with the sort of quoting thunderbird/seamonkey does for HTML >> mail. Maybe thunderbird/seamonkey uses CSS to indent quoted text >> more, and shr doesn't do CSS. > > Well there is also the following: > > (setq mm-text-html-renderer 'gnus-article-html) > > Which is included in gnus and is also better than shr concerning the > issue of CSS. That's exactly the function which will be used when setting `mm-text-html-renderer' to `gnus-w3m'. Anyway, IMHO one should send emails in a format which will surely be understood on the other side. If you correspond with web designers or marketing people, then HTML mail with tons of CSS might be ok but when corresponding with the nerds on usenet or free software mailinglists, you're better off with plain text and ASCII art. ;-) Bye, Tassilo _______________________________________________ auctex-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex-devel
