Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: w3
Date: 03 Dec 1999 12:26:27 -0500	[thread overview]
Message-ID: <86iu2gc4vw.fsf@megalith.bp.aventail.com> (raw)
In-Reply-To: Harry Putnam's message of "03 Dec 1999 09:04:37 -0800"

Harry Putnam <reader@newsguy.com> writes:

> wmperry@aventail.com (William M. Perry) writes:
> 
> > Harry Putnam <reader@newsguy.com> writes:
> > 
> > > Setting up a beta version of xemacs to use gnus [and w3].
> > > 
> > > xemacs version: 21.2.19
> > > w3 version: w3-4.0pre.44
> > > 
> > > Attempts to load w3 result in this error message:
> > > Invalid byte code: "variable reference to constant symbol :group"
> > > 
> > > Anyone know what the fix would be?
> > 
> > Try removing the 'let (...)' in w3-keyword.el... although this code works
> > fine for me here XEmacs 21.2  (beta22) "Mercedes"
> > 
> > I didn't compile with all the debugging whizbangs though.  That might be an
> > issue.
> 
> 
> OOOps  .. think I found the problem... I was aiming xemacs at w3 *.elc
> files compiled with fsf emacs.

Ohhhh, that'll do it.

> A little off the beaten path for ding ...:

> The main reason I am experimenting with xemacs was to see if its
> html-mode, and particularly C-c C-v `browse-url-of-buffer' and the
> toggle C-c C-s that allows you to view edits immediately, would be
> nicer using the built-in  w3 as against fsf emacs with netscape.
> 
> 
> My xemacs loads html-mode alright but balks at `browse-url-of-buffer'
> with:
> Symbols function definition is void: `browse-url-of-buffer'
> 
> Does it work for you?

Never heard of that function... sorry. :)

-bpc


  reply	other threads:[~1999-12-03 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-03 14:32 w3 Harry Putnam
1999-12-03 15:20 ` w3 William M. Perry
1999-12-03 17:04   ` w3 Harry Putnam
1999-12-03 17:26     ` William M. Perry [this message]
1999-12-05  0:15     ` w3 Dave Love

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=86iu2gc4vw.fsf@megalith.bp.aventail.com \
    --to=wmperry@aventail.com \
    --cc=ding@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).