[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Backtrace and message buffer tell me different things

From: Lennart Borgman
Subject: Re: Backtrace and message buffer tell me different things
Date: Sat, 18 Dec 2010 11:51:04 +0100

On Sat, Dec 18, 2010 at 10:32 AM, Andreas Schwab <address@hidden> wrote:
> Lennart Borgman <address@hidden> writes:
>> On Sat, Dec 18, 2010 at 9:38 AM, Andreas Schwab <address@hidden> wrote:
>>> Lennart Borgman <address@hidden> writes:
>>>> I get a strange error from mumamo. The backtrace looks like this:
>>>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>>>   byte-code("..." [buffer table set-syntax-table] 2)
>>>>   #[(body) [strange stuff here...]
>>>>   mumamo-fetch-major-mode-setup(mumamo-bad-mode nil)
>>>>   mumamo-get-major-mode-setup(html-mode)
>>>>   mumamo-new-create-chunk(((1 192 html-mode nil nil nil
>>>> (mumamo-chunk-xml-pi mumamo-chunk-alt-php mumamo-chunk-alt-php=
>>>> mumamo-chunk-inlined-style mumamo-chunk-inlined-script
>>>> mumamo-chunk-style= mumamo-chunk-onjs=) nil nil t) (nil nil nil 0
>>>> nil)))
>>>>   mumamo-find-chunks-1(192 "mumamo-get-chunk-save-buffer-state")
>>>>   mumamo-find-chunks(192 "mumamo-get-chunk-save-buffer-state")
>>>>   mumamo-get-chunk-save-buffer-state(192)
>>>>   mumamo-turn-on-actions(lisp-interaction-mode)
>>>>   html-mumamo-mode()
>>>>   call-interactively(html-mumamo-mode t nil)
>>>>   execute-extended-command(nil)
>>>>   call-interactively(execute-extended-command nil nil)
>>>> However in the message buffer I have this:
>>>>   MU:returning from mumamo-fetch-major-mode-setup
>>>>   MU:after mumamo-fetch-major-mode-setup B
>>> Where is the message on entering?
>> They are before the messages above, just where one would expect them to be.
> So the error occured before the enter message was reached.

Thanks Andreas, your questions made me look at it a different way. I
had assumed that mumamo-fetch-major-mode-setup could not be called
from within itself, but that was not true. (This is not the first time
I have been hit by bad assumptions I have made regarding how font-lock

reply via email to

[Prev in Thread] Current Thread [Next in Thread]