From: Karl Kleinpaste <karl@justresearch.com>
Subject: w3-strict-width again
Date: 17 Nov 1998 17:57:13 -0500 [thread overview]
Message-ID: <vxku2zykjw6.fsf@beaver.jprc.com> (raw)
One of the fixes Lars made for p0.43 was...
* mm-view.el (mm-inline-text): Bind w3-strict-width.
...which is supposed to correct the problem where (window-width) is
less than (frame-width) and text/html parts are erroneously rendered
at (frame-width).
Unfortunately, I think we have a binding-time error. The very first
time that I view a text/html part, it is still rendered as though it
expected that *Article* to be as wide as Emacs. But if I immediately
`g' the same article again, it is re-rendered with an appropriate
width. All subsequent text/html portions seem fine, too, of course.
I suspect that w3-strict-width is bound by Gnus, which then autoloads
W3-related *.elc, which has the effect of altering w3-strict-width
according to the natural expectations of W3. Once the package is
loaded, then subsequent bindings of w3-strict-width by Gnus work fine.
Can this sort of thing be worked around, or is it just something we
have to live with?
Screenshots available in http://www.cs.cmu.edu/~karl/pgnus/html-too-wide.
next reply other threads:[~1998-11-17 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 22:57 Karl Kleinpaste [this message]
1998-11-18 1:13 ` 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=vxku2zykjw6.fsf@beaver.jprc.com \
--to=karl@justresearch.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).