From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook Date: Mon, 21 Aug 2006 09:15:23 +0200 Message-ID: <85lkpia7as.fsf@lola.goethe.zz> References: <2cd46e7f0608181530l1c1a18f7k1923f610edf73f59@mail.gmail.com> <2cd46e7f0608201549h35257287y86202066b04b58ce@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1156146108 31994 80.91.229.2 (21 Aug 2006 07:41:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 21 Aug 2006 07:41:48 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 21 09:41:41 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 1GF4Pd-0002T5-GS for ged-emacs-devel@m.gmane.org; Mon, 21 Aug 2006 09:41:33 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GF4Pc-00012U-SV for ged-emacs-devel@m.gmane.org; Mon, 21 Aug 2006 03:41:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GF4PP-00011n-6k for emacs-devel@gnu.org; Mon, 21 Aug 2006 03:41:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GF4PO-000119-Ib for emacs-devel@gnu.org; Mon, 21 Aug 2006 03:41:18 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GF4PO-000115-Br for emacs-devel@gnu.org; Mon, 21 Aug 2006 03:41:18 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GF4Wj-00044o-5N for emacs-devel@gnu.org; Mon, 21 Aug 2006 03:48:53 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1GF4PG-0002vR-CD; Mon, 21 Aug 2006 03:41:10 -0400 Original-Received: by lola.goethe.zz (Postfix, from userid 1002) id DB2461C4D3AD; Mon, 21 Aug 2006 09:15:23 +0200 (CEST) Original-To: "Ken Manheimer" In-Reply-To: <2cd46e7f0608201549h35257287y86202066b04b58ce@mail.gmail.com> (Ken Manheimer's message of "Sun, 20 Aug 2006 18:49:03 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:58593 Archived-At: "Ken Manheimer" writes: > On 8/20/06, Richard Stallman wrote: >> i would really, really, *really* have liked to backtraces to help >> track this down, but emacs backtraces are useless for that by design. >> you have to know where to put them to get the backtrace from an error >> at that point. >> >> I do not understand that sentence. What do you mean, "put them"? >> What do you mean by "where"--what is a "place"? > > "put them" == put the `(backtrace)' call > "where" == at the point in the code for which you want the backtrace. > > 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. (setq debug-on-signal t) It's not actually a fun setting, since it catches quite a lot, but it is useful. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum