From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook Date: Mon, 21 Aug 2006 07:13:30 -0400 Message-ID: References: <2cd46e7f0608181530l1c1a18f7k1923f610edf73f59@mail.gmail.com> <2cd46e7f0608201549h35257287y86202066b04b58ce@mail.gmail.com> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1156159052 7482 80.91.229.2 (21 Aug 2006 11:17:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 21 Aug 2006 11:17:32 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 21 13:17:31 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GF7mR-0007cx-3w for ged-emacs-devel@m.gmane.org; Mon, 21 Aug 2006 13:17:19 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GF7mQ-0002bC-IV for ged-emacs-devel@m.gmane.org; Mon, 21 Aug 2006 07:17:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GF7il-0006N3-Nm for emacs-devel@gnu.org; Mon, 21 Aug 2006 07:13:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GF7il-0006MP-70 for emacs-devel@gnu.org; Mon, 21 Aug 2006 07:13:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GF7il-0006MB-45 for emacs-devel@gnu.org; Mon, 21 Aug 2006 07:13:31 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GF7q8-0005WM-7H for emacs-devel@gnu.org; Mon, 21 Aug 2006 07:21:08 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1GF7ik-0001mt-BE; Mon, 21 Aug 2006 07:13:30 -0400 Original-To: "Ken Manheimer" In-reply-to: <2cd46e7f0608201549h35257287y86202066b04b58ce@mail.gmail.com> (ken.manheimer@gmail.com) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:58622 Archived-At: "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?