From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: debug-ignored-errors usage Date: Fri, 03 May 2019 16:18:53 -0400 Message-ID: References: <86ef5gw97l.fsf@zoho.eu> <874l6ci60b.fsf@ericabrahamsen.net> <86a7g4w4t0.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="254318"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri May 03 23:13:58 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hMfVA-0012u5-Ox for geh-help-gnu-emacs@m.gmane.org; Fri, 03 May 2019 23:13:52 +0200 Original-Received: from localhost ([127.0.0.1]:46858 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMeeN-0005LB-PR for geh-help-gnu-emacs@m.gmane.org; Fri, 03 May 2019 16:19:19 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMee8-0005Ku-Gf for help-gnu-emacs@gnu.org; Fri, 03 May 2019 16:19:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMee7-0002S3-FH for help-gnu-emacs@gnu.org; Fri, 03 May 2019 16:19:04 -0400 Original-Received: from [195.159.176.226] (port=42290 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hMee7-0002RQ-71 for help-gnu-emacs@gnu.org; Fri, 03 May 2019 16:19:03 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hMee2-000kmA-Q4 for help-gnu-emacs@gnu.org; Fri, 03 May 2019 22:18:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:bTv/+D2sKzFAofgoFR+H7MGhZe0= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120157 Archived-At: > So the debugger is only triggered once per error type? That's probably because you're still in the debugger of the first error, in which case the debugger is temporarily inhibited. > Also, putting beginning-of-buffer in `debug-ignored-errors' still > echoes "Beginning of buffer" in the minibuffer when that happens. Why is that a surprise? Do you really consider echoing "Beginning of buffer" as "debugging"? > but you still get the message every time like always? The error message is there to let the user know about what happened. The debugger is there so you can go and change the code to avoid the error. In the case of beginning-of-buffer, the error is usually not due to a problem in the code, but a problem in the user's action, which is why it's placed in debug-ignored-errors (there's usually no point entering the debugger for that condition since it does not reflect a bug that we'd want to track down). > I don't see the point in seeing the message in > the echo area either. Many/most commands try to make sure that *something* happens in response to the command, so the user knows that the command was indeed executed. Echoing is one way to do that when the command wouldn't do anything else otherwise. Stefan