From: joakim@verona.se
To: Ivan Kanis <expire-by-2011-05-16@kanis.fr>
Cc: emacs-devel-request <emacs-devel@gnu.org>
Subject: Re: SHR bug?
Date: Wed, 11 May 2011 14:25:29 +0200 [thread overview]
Message-ID: <m3fwolctl2.fsf@verona.se> (raw)
In-Reply-To: <8762ph39kx.fsf@kanis.fr> (Ivan Kanis's message of "Wed, 11 May 2011 10:50:06 +0200")
Ivan Kanis <expire-by-2011-05-16@kanis.fr> writes:
> Hi Joakim,
>
> joakim@verona.se wrote:
>
>> I use gnus and SHR to render evil html mail.
>> Currently it fails. Should I report a bug or is it already known?
>
> What's SHR?
It is a new html rendering component available in Gnus. It usually
renders the html in emails quite well!
>
> Take care
--
Joakim Verona
next prev parent reply other threads:[~2011-05-11 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 12:34 SHR bug? joakim
2011-05-10 12:47 ` Julien Danjou
2011-05-10 17:47 ` Ted Zlatanov
2011-05-11 8:50 ` Ivan Kanis
2011-05-11 12:25 ` joakim [this message]
2011-05-11 13:56 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fwolctl2.fsf@verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=expire-by-2011-05-16@kanis.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).