Bug(s)? in current emacs-w3m cvs

[Elias Oltmanns <oltmanns@xxxxxxxxxxx>]

Hello everyone,

actually I wanted to mention in my first post to this list that
emacs-w3m seems to be an excellent tool and I'm liking it more every
day. Yet another feature I discovered just today and which is very
likely going to be another reason for being even more excited about
emacs-w3m is the possibility to choose between lynx like and info like
key bindings. However, I discovered a key binding in the info like set
up which seemed a bit odd to me and so I thought it might be
appropriate to apply the following small patch:

--- w3m.el~	2005-02-27 01:06:43.000000000 +0000
+++ w3m.el	2005-02-27 01:07:48.000000000 +0000
@@ -6327,7 +6327,7 @@
     (define-key map "+" 'w3m-antenna-add-current-url)
     (define-key map "A" 'w3m-antenna)
     (define-key map "b" 'w3m-scroll-down-or-previous-url)
-    (define-key map "c" 'w3m-print-this-url)
+    (define-key map "c" 'w3m-print-current-url)
     (define-key map "!" 'w3m-redisplay-with-content-type)
     (define-key map "d" 'w3m-download)
     (define-key map "D" 'w3m-download-this-url)
More importantly though, emacs-w3m sometimes has problems with
relative links. If I try, for instance, to view [1], I end up on a
page informing me that this target doesn't exist anymore - so far so
good. Strangely enough, neither can I view the source of this page (by
hitting \), nor can I follow the suggested link to another page on the
same server. The error message I get is
Wrong type argument: stringp, nil

Unfortunately I can't come up with a patch for this one. Do you know
what causes problems of this kind.
w3m itself apparently copes with links like this one without any
problem. Not only for that reason is w3m a really magnificent text
browser (sorry, pager) in itself ... something I'd like to point out
too, just in case the w3m author is reading this list too.

Thanks for your help,

Elias