Pat Regan <[EMAIL PROTECTED]> writes: > Pat Regan wrote: >> I am not exactly sure how to troubleshoot this. .xsession-errors >> doesn't show anything when this happens. Is there any way to hook a >> debugger up to Sawfish to see what lisp is running? > > I think I might have either lied, or I was just mistaken :). I do get a > message in .xsession-errors when a window disappears: > > Bad argument: #<subr aref>, (), 1
> Is there any way I can track down exactly which function is receiving a > bad argument? Or find out where it is being called from? to get more info, use: (setq backtrace-on-error #t) do this (prompt) (you type): ------------------------- bash$ sawfish-client user> (setq backtrace-on-error #t) t user> ^D bash$ These should be already on: (setq error-handler-beep #t) to verify: user> error-handler-beep t would be ok () that means it would not beep.
