Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-w3m@namazu.org
Subject: Re: emacs-w3m
Date: Thu, 24 Jan 2002 12:26:19 +0900	[thread overview]
Message-ID: <yosu3d0wctus.fsf@jpl.org> (raw)
In-Reply-To: <87lmeo1mxw.fsf@inanna.rimspace.net>

;; <emacs-w3m@namazu.org> is the open list, so you have no need
;; to exclude it from the recipients list.  "MCT: never" means
;; don't include me in the list. :-)

Hi,

Thanks Daniel for the comments.

>>>>> In <87lmeo1mxw.fsf@inanna.rimspace.net>
>>>>>	Daniel Pittman <daniel@rimspace.net> wrote:

> Some stylistic comments, but no real objection -- it would be
> great to see better support for multiple rendering engines.

I see.  It is natural.

KY> * mm-decode.el (mm-inline-text-use-emacs-w3m): New user option.

> Would it be possible to create `mm-inline-text-html-renderer' or
> similar, which took a function to call passing the MIME handle, etc?

> That way you could define `...-render-with-w3', `...-render-with-w3m'
> and also any other HTML rendering solution that became desirable.

KY>  (mm-inline-media-tests): Check for w3m instead of w3 if
KY> `mm-inline-text-use-emacs-w3m' is non-nil.

> You could set the default value for the above variable to the
> w3 version if it's found, or w3m next.

Good idea!  I will do so.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



  reply	other threads:[~2002-01-24  3:26 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   ` Katsumi Yamaoka [this message]
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       ` emacs-w3m François Pinard
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=yosu3d0wctus.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=emacs-w3m@namazu.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).