From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: Can't fine mime.parse
Date: Sun, 14 Nov 2010 15:29:25 +0100 [thread overview]
Message-ID: <m3eiaox9kq.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <8739r8hqzu.fsf@engels.HistoricalMaterialism.info>
Haines Brown <haines@HistoricalMaterialism.info> writes:
> I installed emacs-w3m and put these lines into .emacs:
>
> "~/elisp/w3m/"
>
> (require 'w3m-load)
That shouldn't be necessary...
> (require 'mime-w3m)
And that doesn't sound correct.
> There is available a mime-parse.el, but I had assumed that this was
> automatically a part of emacs 23. Should I go ahead and install
> mime-parse (along with its dependencies: mime-def, luna and std11)? My
> intuition is that this is not necessary just to get emacs to desplay
> html files with w3m.
(setq mm-text-html-renderer 'w3m)
should be sufficient -- you shouldn't have to require anything. But you
have to install w3m, of course.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-11-14 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 14:30 Haines Brown
2010-11-14 14:29 ` Lars Magne Ingebrigtsen [this message]
2010-11-14 17:32 ` Haines Brown
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=m3eiaox9kq.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).