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: Problems with debug-on-entry in the Lisp debugger. Date: Wed, 09 Mar 2005 11:58:47 -0500 Message-ID: References: <87sm37n2bv.fsf@xs4all.nl> <87is42c8yp.fsf@xs4all.nl> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1110388345 24535 80.91.229.2 (9 Mar 2005 17:12:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Mar 2005 17:12:25 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 09 18:12:24 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D94fm-000759-9f for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2005 18:08:38 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D94uP-0002v7-5d for ged-emacs-devel@m.gmane.org; Wed, 09 Mar 2005 12:23:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D94rc-00012B-7T for emacs-devel@gnu.org; Wed, 09 Mar 2005 12:20:52 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D94rV-0000zh-TU for emacs-devel@gnu.org; Wed, 09 Mar 2005 12:20:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D94rU-0000p0-Rx for emacs-devel@gnu.org; Wed, 09 Mar 2005 12:20:44 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D94WF-0000e8-QY for emacs-devel@gnu.org; Wed, 09 Mar 2005 11:58:47 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1D94WF-00066T-F2; Wed, 09 Mar 2005 11:58:47 -0500 Original-To: Lute Kamstra In-reply-to: <87is42c8yp.fsf@xs4all.nl> (message from Lute Kamstra on Tue, 08 Mar 2005 19:02:06 +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: news.gmane.org gmane.emacs.devel:34379 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34379 Below is a quick "proof-of-concept" patch for src/eval.c and lisp/emacs-lisp/debug.el to get a better idea of what I mean. As you can see, the change to eval.c isn't that big. The code is not unclean, but I don't think it is a real problem that the debug-on-entry code is visible. So I'd rather not go in this direction. This is not the part of Emacs that is important to improve. Hackers tend to focus their attention on the parts of Emacs that make it seem more elegant in programmers' terms, but this doesn't make Emacs more powerful or a better editor. Could you possibly look at implementing something listed in etc/TODO?