Re: Which-function-mode is turning itself off

[Kim F. Storm]

<address@hidden> writes:

> How shall we proceed?

Don't quite know, except that there really isn't much reason to
turn it off because of an error...

Your backtrace shows an "interesting" problem:

> * which-func-mode(-1)
>   byte-code("???\"?" [info which-func-mode -1 error "Error in 
> which-func-update: %s"] 3)
>   which-func-update-1(#<window 16 on *Occur-N50S*>)
>   which-func-update()
>   apply(which-func-update nil)
>   (condition-case nil (apply (aref timer 5) (aref timer 6)) (error nil))
>   (let (retrigger) (cancel-timer timer) (if (aref timer 4) (if ... ... ... 
> ... ... ...)) (condition-case nil (apply ... ...) (error nil)) (if retrigger 
> (aset timer 0 nil)))
>   (if (timerp timer) (let (retrigger) (cancel-timer timer) (if ... ...) 
> (condition-case nil ... ...) (if retrigger ...)) (error "Bogus timer event"))
>   (let ((inhibit-quit t)) (if (timerp timer) (let ... ... ... ... ...) (error 
> "Bogus timer event")))
>   timer-event-handler([t 0 0 500000 t which-func-update nil t])
>   input-pending-p()

Does it really make sense for input-pending-p to run timers?
And if so, should it run them while we are already running timers?

>   byte-code(""
>   jit-lock-stealth-fontify()
>   apply(jit-lock-stealth-fontify nil)
>   (condition-case nil (apply (aref timer 5) (aref timer 6)) (error nil))
>   (let (retrigger) (cancel-timer timer) (if (aref timer 4) (if ... ... ... 
> ... ... ...)) (condition-case nil (apply ... ...) (error nil)) (if retrigger 
> (aset timer 0 nil)))
>   (if (timerp timer) (let (retrigger) (cancel-timer timer) (if ... ...) 
> (condition-case nil ... ...) (if retrigger ...)) (error "Bogus timer event"))
>   (let ((inhibit-quit t)) (if (timerp timer) (let ... ... ... ... ...) (error 
> "Bogus timer event")))
>   timer-event-handler([t 0 0 500000 t jit-lock-stealth-fontify nil t])

-- 
Kim F. Storm <address@hidden> http://www.cua.dk