Re: [PATCH] `disabled-command-hook' fix (was Re: Really weird `disabled-command-hook' bug)
On Sat, 19 Jan 2002, Hrvoje Niksic uttered the following:
Nix <nix(a)esperi.demon.co.uk> writes:
> Anyway, the bug is that, in command_execute(), the hook is run by
> passing the *variable* to run_hook(), not the symbol pointing at the
> variable.
But that should still work, as long as the variable is tied to the
symbol using DEFVAR_LISP, right?
What can I say but `it doesn't seem to' :)
(Note that there was *no* Qdisabled_command_hook variable present; I
don't know if this would break that tying because I don't know how the
tying works :) )
--
`I personally would not stand in a river waving a graphite rod above my
head during a thunderstorm.' --- Harry Jackson