"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Ie, it's required, but the error should be caught and ignored.
Are you sure you have no other versions of w3 installed?
Actually, I've noticed that a different error is occurring now. My apologies if
I did not provide the correct backtrace before, I'm pretty new at this.
I load do M-x w3 RET and get the following error/backtrace:
Signaling: (wrong-type-argument number-char-or-marker-p nil)
+(nil 12)
font-spatial-to-canonical("+12pt")
css-expand-length("+12pt" t)
css-expand-value(height "+12pt")
css-parse-args(238 257)
css-parse("file:/usr/local/lib/xemacs/xemacs-packages/etc/w3/stylesheet" nil
nil)
w3-find-default-stylesheets()
w3-refresh-stylesheets()
w3-do-setup()
#<compiled-function nil "...(62)" [w3-track-last-buffer w3-setup-done
w3-last-buffer w3-default-homepage w3-do-setup bufferp buffer-name switch-to-buffer
message "Reusing buffer. To reload, type %s." substitute-command-keys
"\\[w3-reload-document]" call-interactively w3-fetch error "Invalid setting
for w3-default-homepage: %S" string-match ".*:.*" "file:"] 4
("/usr/local/lib/xemacs/xemacs-packages/lisp/w3/w3.elc" . 30891) nil>()
call-interactively(w3)
command-execute(w3 t)
execute-extended-command(nil)
call-interactively(execute-extended-command)
This looks more like a font problem, and I am indeed using some bitmap fonts
that could be causing this. On a hunch, I did M-x w3 RET from xemacs -q, and w3
loaded just fine. Clearly, the problem is from my own settings. What I'd like
to know is how I go about finding the culprit and fixing the problem? :)
Thanks in advance.
-j
--
Joel Stanley * jstanley(a)cs.uiuc.edu