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: Sun, 20 Aug 2006 08:05:38 -0400 Message-ID: References: <2cd46e7f0608181530l1c1a18f7k1923f610edf73f59@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 1156075911 31174 80.91.229.2 (20 Aug 2006 12:11:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 20 Aug 2006 12:11:51 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 20 14:11:49 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 1GEm9Y-00080V-3V for ged-emacs-devel@m.gmane.org; Sun, 20 Aug 2006 14:11:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GEm9X-0004W0-CX for ged-emacs-devel@m.gmane.org; Sun, 20 Aug 2006 08:11:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GEm3j-0006qb-Ew for emacs-devel@gnu.org; Sun, 20 Aug 2006 08:05:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GEm3g-0006lp-Cy for emacs-devel@gnu.org; Sun, 20 Aug 2006 08:05:40 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GEm3f-0006lH-PE for emacs-devel@gnu.org; Sun, 20 Aug 2006 08:05:39 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GEmAp-0002en-5i for emacs-devel@gnu.org; Sun, 20 Aug 2006 08:13:03 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1GEm3e-0006P2-Sx; Sun, 20 Aug 2006 08:05:38 -0400 Original-To: "Ken Manheimer" In-reply-to: <2cd46e7f0608181530l1c1a18f7k1923f610edf73f59@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:58549 Archived-At: 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"? however, i can't understand not having a mode - eg, with a `debug-on-error' style variable, eg `retain-backtrace-on-error' - for retaining backtraces on any error, to be replaced when the next error happens. We could do that easily, I suppose, but could you explain how it relates to the problem?