Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: info-gnus-english@gnu.org
Subject: Re: HTML Emails
Date: Thu, 18 Oct 2007 09:21:20 +0200	[thread overview]
Message-ID: <v96414nb0v.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3myuhdw6f.fsf@ieee.org>

On Thu, Oct 18 2007, Randy Yates wrote:

> Randy Yates <yates@ieee.org> writes:
>
>> I mostly love the way gnus allows me to use xemacs to read and respond
>> to usenet articles and email messages, but I hate the way it currently
>> handles HTML emails. They are currently interpreted by xemacs internally
>> (I think by w3) and it does a horrible job. 
>>
>> Can someone suggest a way to spawn Firefox to read html messages, 

Only in the development version (`gnus-article-browse-html-article' is
on K H, <menu-bar> <Article> <MIME> <Multipart> <View HTML parts in
browser>):

,----[ <f1> f gnus-article-browse-html-article RET ]
| gnus-article-browse-html-article is an interactive compiled Lisp
| function in `gnus-art.el'.
| (gnus-article-browse-html-article)
| 
| View "text/html" parts of the current article with a WWW browser.
| 
| Warning: Spammers use links to images in HTML articles to verify
| whether you have read the message.  As
| `gnus-article-browse-html-article' passes the unmodified HTML
| content to the browser without eliminating these "web bugs" you
| should only use it for mails from trusted senders.
`----

>> or can they otherwise suggest a better, more up-to-date method for
>> handling html?

Most people like `w3m' (emacs-w3m)...

,----[ (info "(emacs-mime)Display Customization") ]
| `mm-text-html-renderer'
|      This selects the function used to render HTML.  The predefined
|      renderers are selected by the symbols `w3', `w3m'(1), `links',
|      `lynx', `w3m-standalone' or `html2text'.  If `nil' use an external
|      viewer.  You can also specify a function, which will be called
|      with a MIME handle as the argument.
`----

> "Gnus v5.10.7" "XEmacs 21.4 (patch 20) \"Double Solitaire\" [Lucid]
> (x86_64-unknown-linux, Mule)

Please upgrade to Gnus 5.10.8 available from the XEmacs packages tree.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

      parent reply	other threads:[~2007-10-18  7:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18  1:52 Randy Yates
2007-10-18  1:54 ` Randy Yates
2007-10-18  4:07   ` slack-rat
2007-10-18  7:14     ` Tassilo Horn
     [not found]     ` <mailman.2231.1192691693.18990.info-gnus-english@gnu.org>
2007-10-18 17:59       ` Randy Yates
2007-10-18 18:11         ` Randy Yates
2007-10-19 12:05           ` Tassilo Horn
     [not found]           ` <mailman.2291.1192795535.18990.info-gnus-english@gnu.org>
2007-10-19 14:31             ` Randy Yates
2007-10-20 14:50               ` Randy Yates
2007-10-20 16:42                 ` Tassilo Horn
     [not found]                 ` <mailman.2359.1192898563.18990.info-gnus-english@gnu.org>
2007-10-20 18:31                   ` Randy Yates
2007-10-20 15:27               ` Tassilo Horn
2007-10-18  7:21   ` Reiner Steib [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v96414nb0v.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=info-gnus-english@gnu.org \
    /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.
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 NNTP newsgroup(s).