From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: text/html rendering erroneously uses frame-width
Date: 13 Nov 1998 15:45:04 -0500 [thread overview]
Message-ID: <vxkyapfxqy7.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "13 Nov 1998 20:09:13 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> But it doesn't call that from the buffer that it's actually
> displayed in. It does a `with-temp-buffer' and reders the thing there
> before copying over. Could that be a source of the problem?
Perhaps. The important fact is that whatever function is in charge of
geometry of rendering has to know the size of the actual *Article*
buffer where the result is destined to land. This might be
complicated by the fact that *Article* may not even exist yet when
rendering is begun. I'm afraid I'm at a bit of a loss just now to
find in w3/*.el exactly how the (currently wrong) choice is being made.
prev parent reply other threads:[~1998-11-13 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-12 15:59 Karl Kleinpaste
1998-11-13 19:09 ` Lars Magne Ingebrigtsen
1998-11-13 20:11 ` William M. Perry
1998-11-13 21:29 ` Lars Magne Ingebrigtsen
1998-11-13 20:45 ` Karl Kleinpaste [this message]
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=vxkyapfxqy7.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.com \
/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).