bug#7769: Void variable nxml-mode-map when running nXhtml tests

bug#7769: Void variable nxml-mode-map when running nXhtml tests

[Lennart Borgman]

I found a problem with nxml-mode.el when testing nXhtml. If nXhtml is
not byte compiled it works fine, but when it is byte compiled some
tests fails with "void variable nxml-mode-map".

With an Emacs checkout from 2010-11-23 all tests pass, but with a
checkout from 2010-12-15 some tests fail as above.

I think the problem is caused by a small part of this change:

  2010-12-03  Glenn Morris  <rgm@gnu.org>

	* nxml/nxml-mode.el: Require rng-nxml.
	(rng-nxml-mode-init, nxml-enable-unicode-char-name-sets):
	Remove declarations.

This change moved the (provide 'nxml-mode) statement to the beginning
of nxml-mode.el. Since eval-after-load is run at the provide the
statement

(eval-after-load 'nxml-mode
  '(progn
     (define-key nxml-mode-map [C-M-left]  'nxml-backward-element)
     (define-key nxml-mode-map [C-M-right] 'nxml-forward-element)
     (define-key nxml-mode-map [C-M-up]    'nxml-backward-up-element)
     (define-key nxml-mode-map [C-M-down]  'nxml-down-element)))

in the nXhtml file nxhtml-mode.el will now be run before nxml-mode-map
is defined.

bug#7769: Void variable nxml-mode-map when running nXhtml tests

[Glenn Morris]

This kind of thing is explained in the doc-string of eval-after-load.
Use a string instead of a symbol for the FILE argument.

bug#7769: Void variable nxml-mode-map when running nXhtml tests

[Stefan Monnier]

> This kind of thing is explained in the doc-string of eval-after-load.
> Use a string instead of a symbol for the FILE argument.

BTW, I've just installed a change in the trunk to fix this problem
(i.e. so that eval-after-load evals *after-load* even for features that
are provided at the beginning (or in the middle) of the file).


        Stefan