From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Lisp debugger problems. Date: Mon, 28 Feb 2005 06:26:00 -0500 Message-ID: References: <878y5eke1b.fsf@xs4all.nl> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1109593828 8084 80.91.229.2 (28 Feb 2005 12:30:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 28 Feb 2005 12:30:28 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 28 13:30:28 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D5k2K-0003EI-I3 for ged-emacs-devel@m.gmane.org; Mon, 28 Feb 2005 13:30:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5kKg-0002Rw-FF for ged-emacs-devel@m.gmane.org; Mon, 28 Feb 2005 07:49:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D5jYg-0008Al-6d for emacs-devel@gnu.org; Mon, 28 Feb 2005 06:59:31 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D5jYd-0008AD-86 for emacs-devel@gnu.org; Mon, 28 Feb 2005 06:59:28 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D5jW5-0007bz-Kn for emacs-devel@gnu.org; Mon, 28 Feb 2005 06:56:50 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D5j3l-0007Js-4F for emacs-devel@gnu.org; Mon, 28 Feb 2005 06:27:33 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1D5j2G-0003vu-ND; Mon, 28 Feb 2005 06:26:00 -0500 Original-To: Lute Kamstra In-reply-to: <878y5eke1b.fsf@xs4all.nl> (message from Lute Kamstra on Thu, 24 Feb 2005 01:16:48 +0100) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33913 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33913 What I don't understand in why debug-on-entry and cancel-debug-on-entry call debugger-reenable as well (thus causing the strange behavior in the example above). What am I missing? I am not certain. Perhaps the idea was in case you do debugger-jump but you don't reenter the debugger. In that case, debugger entry would be turned off permanently in those functions. If so, this solution is just a half measure. We really should arrange to reenable debugger entry for these functions whenever control gets back to the command level outside the debugger. This could be done by frobbing post-command-hook somehow. Meanwhile, it would be nice and clean if redefining a function with defun, defmacro, defsubst or defalias were smart enough to turn debug-on-entry back on if it was on before. Want to do that?