Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: w3-strict-width again
Date: 18 Nov 1998 02:13:17 +0100	[thread overview]
Message-ID: <m3d86lst02.fsf@sparky.gnus.org> (raw)
In-Reply-To: Karl Kleinpaste's message of "17 Nov 1998 17:57:13 -0500"

Karl Kleinpaste <karl@justresearch.com> writes:


> 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.

Hm.  Well, I've now `require'd w3-vars first, but I'm not sure this is 
the cause of the problem.  It might be a redisplay problem -- that the 
article buffer window hasn't been rendered when you view the article
the first time, or something like that...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


      reply	other threads:[~1998-11-18  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-17 22:57 Karl Kleinpaste
1998-11-18  1:13 ` Lars Magne Ingebrigtsen [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=m3d86lst02.fsf@sparky.gnus.org \
    --to=larsi@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).