From: Andrea Venturoli <ml.diespammer@netfence.it>
To: help-gnu-emacs@gnu.org
Subject: Debugger nag
Date: Fri, 24 Sep 2010 11:10:03 GMT [thread overview]
Message-ID: <fG%mo.210998$9f6.441940@twister1.libero.it> (raw)
Hello.
I've recently installed nxhtml (which helped me a lot on some web projects).
However, since then, every single trivial error brings up a stack trace
window.
E.g. I have a key assigned to compilation-next-error, so, after compile,
I'll keep pressing that key.
When at the end, I used to get a warning sound and a simple message; now
I always get a verbose windows with:
Debugger entered--Lisp error: (error "Moved past last error")
signal(error ("Moved past last error"))
error("Moved past last %s" "error")
compilation-next-error(1 nil #<marker at 44578 in *compilation*>)
compilation-next-error-function(1 nil)
next-error(nil)
call-interactively(next-error nil nil)
How can I restore the old behaviour (without removing nxhtml)?
bye & Thanks
av.
next reply other threads:[~2010-09-24 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 11:10 Andrea Venturoli [this message]
2010-09-25 1:00 ` Debugger nag Tim X
[not found] ` <xjlno.211352$9f6.443800@twister1.libero.it>
2010-09-25 17:32 ` Andreas Politz
2010-09-27 7:41 ` Andrea Venturoli
2010-09-27 7:44 ` Andrea Venturoli
2010-09-26 22:11 ` Tim X
2010-09-27 7:42 ` Andrea Venturoli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fG%mo.210998$9f6.441940@twister1.libero.it' \
--to=ml.diespammer@netfence.it \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).