From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook
Date: Mon, 21 Aug 2006 07:13:30 -0400 [thread overview]
Message-ID: <E1GF7ik-0001mt-BE@fencepost.gnu.org> (raw)
In-Reply-To: <2cd46e7f0608201549h35257287y86202066b04b58ce@mail.gmail.com> (ken.manheimer@gmail.com)
"put them" == put the `(backtrace)' call
"where" == at the point in the code for which you want the backtrace.
To put in an explicit call to (backtrace) is an unusual technique, but
I don't see why it would not work. Since it outputs to
standard-output, you could save multiple backtraces in one buffer.
what i want, instead, is the ability to get a stack trace for an error
when i am handling that error, in a condition-case or in the
interactive interpreter.
Does (setq debug-on-signal t) do what you want?
If not, precisely how does what you want differ from that?
next prev parent reply other threads:[~2006-08-21 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 22:30 blink-cursor-end sometimes fails and disrupts pre-command-hook Ken Manheimer
2006-08-19 15:07 ` Chong Yidong
[not found] ` <87veoo95zy.fsf@furball.mit.edu>
[not found] ` <2cd46e7f0608190731j6247e8bbr7f7f8d1ecb6ac3ce@mail.gmail.com>
[not found] ` <87r6zc9475.fsf@furball.mit.edu>
[not found] ` <2cd46e7f0608190805x70bd8715n6f1b552d57a80a5c@mail.gmail.com>
2006-08-19 15:16 ` Chong Yidong
2006-08-19 15:58 ` Ken Manheimer
2006-08-19 16:15 ` Chong Yidong
2006-08-19 16:59 ` Ken Manheimer
2006-08-21 15:36 ` Stuart D. Herring
2006-08-20 12:05 ` Richard Stallman
2006-08-20 22:49 ` Ken Manheimer
2006-08-21 7:15 ` David Kastrup
2006-08-21 11:13 ` Richard Stallman [this message]
2006-08-21 15:31 ` Ken Manheimer
2006-08-21 17:23 ` Stuart D. Herring
2006-08-22 21:12 ` Ken Manheimer
2006-08-23 14:45 ` Richard Stallman
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=E1GF7ik-0001mt-BE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).