[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX-devel] off-topic:html messages

From: Tassilo Horn
Subject: Re: [AUCTeX-devel] off-topic:html messages
Date: Wed, 09 Sep 2015 17:30:59 +0200
User-agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.50 (gnu/linux)

Uwe Brauer <address@hidden> writes:

Hi Uwe,

> I am sorry for having sent html email before, I hope my
> thunderbird/seamonkey configuration is now set correctly.

If you had used thunderbird/seamonkey for this mail, I could have told
you. ;-)

> There is one issue out of curiousity: I looked in my gmail sent folder
> into the message in question.  However when I used reply I had none of
> the problems Tassilo, who also uses gnus, talked about.

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?

> I have the following setting:
> (setq
>  gnus-inhibit-mime-unbuttonizing nil

That's the default value.

>  gnus-mime-display-multipart-alternative-as-mixed nil

Also the default value.

>  gnus-mime-display-multipart-related-as-mixed nil

Also the default value.

>  gnus-mime-display-multipart-as-mixed nil

Also the default value.

>  gnus-buttonized-mime-types nil

Also the default value.

>  mm-discouraged-alternatives nil

That's again the default, but here I have set ("text/html"
"text/richtext") in order to prefer the text/plain part in multipart
alternative messages.

>  gnus-buttonized-mime-types '("multipart/signed" "multipart/encrypted")

I stuck with the default value of nil.

>  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
require external programs.  It usually does a very good job but seems to
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.

>  mm-url-use-external t)

I use the stock elisp url but that shouldn't make any difference wrt
this issue.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]