Re: Help debugging backtrace

["Alex Bennée" <kernel-hacker@bennee.com>]

michael_heerdegen@web.de writes:

> Alex Bennée <kernel-hacker@bennee.com> writes:
>
>> crmbk-frame-mode: cleaning up, running hooks: (crmbk-reset-search
>> crmbk-reenable-touchpad crmbk-remove-powerd-hooks) Error during
>> redisplay: (run-hook-with-args crmbk-delete-frame-handler #<frame Edit
>> Server Frame 0x3830530>) signaled (invalid-function (lambda "Clean-up
>> any hooks into powerd and it's dbus interface" (message (format "in
>> crmbk-remove-powerd-hooks: %s" post-command-hook)) (remove-hook (quote
>> post-command-hook) (quote crmbk-notify-powerd-user-activity)) (message
>> "done")))
>
> This error message says that an invalid function was called.  It is this
> one (you're missing to specify the argument list):
>
> (defun crmbk-remove-powerd-hooks
>   "Clean-up any hooks into powerd and it's dbus interface"
>   (remove-hook 'post-command-hook 'crmbk-notify-powerd-user-activity))

Ahh seems so obvious now, I should have noticed. I was surprised though:

(defun my-test-defun
  "This is a test"
  (message " in my test"))

(defun my-test-defun2 ()
  "This is a test"
  (message " in my test 2"))

You can happily C-x C-e eval-last-sexp both of those defuns without
complaint. The error in the defun only shows up when you try and execute them.

-- 
Alex Bennée