I am not sure how this is expected to work, but i was expecting this line in the definitionof w3m-key-binding
:
`(setq w3m-mode-map (if (eq ,value 'info)
to be instead
`(setq w3m-mode-map (if (eq ',value 'info)
please note the quote in ',value
, which is missing in the current code, so that an invocation
of the form:
(customize-set-variable 'w3m-key-binding 'info)
would work as expected (i.e., set w3m-key-binding to the symbol info
, plus its
other duites). With the current definition (without the quote in ,value
), evaluating
the customize-set-variable
call above throws an error (quite naturally) because the
variable info
is not defined. The same thing happens if one tries the customize interface.
Is this a genuine bug?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.