From: Greg Stark <gsstark@mit.edu>
Subject: Re: w3 rendering
Date: 14 Nov 1999 14:51:15 -0500 [thread overview]
Message-ID: <87hfiozwb0.fsf@HSE-Montreal-ppp19485.qc.sympatico.ca> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "09 Nov 1999 15:21:53 +0100"
Why not pass the parsed structure to W3 directly and have it render it right
away instead of putting text into a buffer and having W3 read that text? Even
if the text is lisp it's still unnecessary overhead.
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> wmperry@aventail.com (William M. Perry) writes:
>
> > You mean you want to insert it as raw HTML, or just directly draw what
> > you've already filtered out?
>
> Insert it as raw HTML.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> larsi@gnus.org * Lars Magne Ingebrigtsen
>
--
greg
next prev parent reply other threads:[~1999-11-14 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-09 6:47 Lars Magne Ingebrigtsen
1999-11-09 10:39 ` Eric Marsden
1999-11-09 14:21 ` Lars Magne Ingebrigtsen
1999-11-09 15:13 ` William M. Perry
1999-11-10 4:15 ` Lars Magne Ingebrigtsen
1999-11-09 12:12 ` William M. Perry
1999-11-09 14:21 ` Lars Magne Ingebrigtsen
1999-11-14 19:51 ` Greg Stark [this message]
1999-11-15 19:53 ` Lars Magne Ingebrigtsen
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=87hfiozwb0.fsf@HSE-Montreal-ppp19485.qc.sympatico.ca \
--to=gsstark@mit.edu \
/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).