From: Randy Yates <yates@ieee.org>
To: info-gnus-english@gnu.org
Subject: Re: HTML Emails
Date: Thu, 18 Oct 2007 14:11:02 -0400 [thread overview]
Message-ID: <m3abqg70p5.fsf@ieee.org> (raw)
In-Reply-To: <m3lka0e22g.fsf@ieee.org>
Randy Yates <yates@ieee.org> writes:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> slack-rat <gnus@azurservers.com> writes:
>>
>> Hi,
>>
>>> in .gnus, this works for me:
>>>
>>> ;; Show the text/plain part of a multipart
>>> (setq mm-discouraged-alternatives
>>> '("text/html"
>>> "text/richtext"))
>>
>> This will only preventy you from seeing the html part if a plain text
>> part is present in multipart messages.
>>
>>> ;; I would like gnus to always use Netscape/mozilla/etc
>>> (setq browse-url-browser-function 'browse-url-firefox)
>>
>> And this affects only which browser to use when hitting RET on a link.
>>
>> I use emacs-w3m [1] to render html mails inside emacs.
>>
>> (setq mm-text-html-renderer 'w3m)
>> (setq mm-inline-text-html-with-images t)
>> (setq mm-inline-large-images t)
>
> Hi Tasilo,
Sorry, that should be "Tassilo."
> I appreciate your response and the information you provided, but
> I don't want to use w3m. I want to use firefox. This is because
> (correct me if I'm wrong) firefox is more likely to have a more
> complete implementation of html in all of its complexities than
> w3m.
>
> I tried substituting "firefox" for "w3m" but that didn't work. It
> also seems there are many "sub-options" for the html rendering and
> the entire mechanism is very confusing to me because I haven't seen
> a document that ties all of these together from a top-level operational
> point-of-view.
>
> Any further information would be appreciated.
What I really would like to do is is bit more involved. While I'm
not a total stranger to lisp, my lisp programming skills are weak
(and my familiarity with xemacs/gnus lisp programming isn't all
that great either), so any leads/programming examples would be
appreciated.
What I'd like to do is, when I'm in the summary buffer, have the
body of all HTML messages suppressed - only the sender, subject,
etc. (i.e., the header) should be displayed. Then if I decide
it's from a trusted source, I'll invoke a key sequence to spawn
firefox to read the message.
How to do?
PS: When I substituted "firefox" for "w3m" I get
Wrong type argument: listp, firefox
in the minibuffer.
--
% Randy Yates % "She's sweet on Wagner-I think she'd die for Beethoven.
%% Fuquay-Varina, NC % She love the way Puccini lays down a tune, and
%%% 919-577-9882 % Verdi's always creepin' from her room."
%%%% <yates@ieee.org> % "Rockaria", *A New World Record*, ELO
http://www.digitalsignallabs.com
next prev parent reply other threads:[~2007-10-18 18:11 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 [this message]
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
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=m3abqg70p5.fsf@ieee.org \
--to=yates@ieee.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).