Geek Answers Handbook

Emacs23 calls the debugger too often

Since I upgraded to Ubuntu lucid and emacs23, Emacs pulls out a debugger in situations where emacs22 does not.

For example, when you click Cc Cc in org-mode, emacs22 simply sets can do nothing useful at this location , while a debugger appears in emacs23.

  Debugger entered--Lisp error: (error "Cc Cc can do nothing useful at this location") signal(error ("Cc Cc can do nothing useful at this location")) error("Cc Cc can do nothing useful at this location") org-ctrl-c-ctrl-c(nil) call-interactively(org-ctrl-c-ctrl-c nil nil)

This only illustrates the pattern - the behavior is not limited to org mode. It happens every 3 minutes, it really annoys me. How can I prevent this?

I already tried to stop this with debug-on-error and stack-trace-on-error : it did not work.

+7
emacs upgrade emacs23
source share
1 answer

Most likely, after setting up, you set debug-on-error.

Some ways to confirm:

Run Org mode, press Cc Cc to enter the debugger, and q to exit again. Now Mx set-variable RET debug-on-error RET nil RET and try again.

Then try running emacs with the -q argument (to avoid executing the initialization file), and then go into org mode and press Cc Cc . This should not cause a debugger.

You can use Mx rgrep RET debug-on-error RET (or perhaps debug-on-error t ) in your lisp directories and custom lisp directories to help keep track of which library is responding.

How could I repeat your problem, I just did it for myself. For me, the culprit was: (load "nxhtml/autostart.el") . I am updating nxhtml now and I suspect that I will allow this in my case.

Edit: or not.

The current version of nxhtml moved the statement from autoload.el to nxhtml-base.el. If this is the same culprit for you, you can either edit this file or make sure that your variable setting occurs after the autostart nxhtml file is executed.

+8
source share

More articles:


All Articles