From: pinard@iro.umontreal.ca (François Pinard)
Cc: ding@gnus.org
Subject: Re: emacs-w3m
Date: 12 Feb 2002 14:27:22 -0500 [thread overview]
Message-ID: <oqg0464i1x.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: <87n0ye5yku.fsf@deneb.enyo.de>
[Florian Weimer]
> pinard@iro.umontreal.ca (François Pinard) writes:
> > [Florian Weimer]
> >
> >> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> >
> >> > Why don't we use emacs-w3m for converting text/html parts on Gnus?
> >
> >> Using w3m might have some nasty security implications (much like the
> >> embedded Internet Explorer in Microsoft Outlook).
> >
> > Please elaborate. :-)
> I don't trust w3m, it has a remarkable security record.
Your remark does not bring new information. By "please elaborate", I was
inviting my correspondent to provide some facts on which an opinion could
be based, that is, more than the re-statement of an intuition or emotion...
Do you have some URL, pointer, flaw description, that could be verified?
`w3m' seems really speedy, and does reasonable work for tables, and at
least a little something for frames, so I would not like giving it up.
Let's see the real nature of the danger, and if there is anything serious,
if `w3m' could be salvaged -- it is most probably worth some effort! :-)
--
François Pinard http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~2002-02-12 19:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 2:38 emacs-w3m Katsumi Yamaoka
2002-01-24 2:51 ` emacs-w3m Daniel Pittman
2002-01-24 3:26 ` emacs-w3m Katsumi Yamaoka
2002-01-24 6:11 ` emacs-w3m Katsumi Yamaoka
2002-01-25 13:29 ` emacs-w3m Niels Olof Bouvin
2002-01-25 18:15 ` emacs-w3m Josh Huber
2002-01-26 2:40 ` emacs-w3m Jinhyok Heo
2002-01-26 3:07 ` emacs-w3m ShengHuo ZHU
2002-01-24 13:37 ` emacs-w3m Per Abrahamsen
2002-01-24 11:28 ` emacs-w3m Jinhyok Heo
2002-01-25 1:28 ` emacs-w3m Katsumi Yamaoka
2002-01-25 2:34 ` emacs-w3m Katsumi Yamaoka
2002-01-25 3:05 ` emacs-w3m Jinhyok Heo
2002-01-25 2:41 ` emacs-w3m Jinhyok Heo
2002-01-24 22:19 ` emacs-w3m Florian Weimer
2002-01-24 22:49 ` emacs-w3m François Pinard
2002-01-26 22:36 ` emacs-w3m Steinar Bang
2002-01-28 2:36 ` emacs-w3m Patric Mueller
2002-01-28 11:32 ` emacs-w3m Katsumi Yamaoka
2002-01-31 15:48 ` emacs-w3m Dirk Meyer
2002-02-01 8:09 ` emacs-w3m Katsumi Yamaoka
2002-02-06 13:29 ` emacs-w3m Dirk Meyer
2002-02-12 18:45 ` emacs-w3m Florian Weimer
2002-02-12 19:27 ` François Pinard [this message]
2002-01-24 23:10 ` emacs-w3m Katsumi Yamaoka
2002-01-27 1:33 ` emacs-w3m Raja R Harinath
2002-01-28 1:30 ` emacs-w3m Katsumi Yamaoka
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=oqg0464i1x.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--cc=ding@gnus.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).