From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How can I rethrow an error after recording a backtrace? Date: Sat, 06 Aug 2016 13:03:23 +0300 Message-ID: <83y44ajjtg.fsf@gnu.org> References: <53ca9864-3a3b-8406-65c9-8458d0512299@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1470477836 977 195.159.176.226 (6 Aug 2016 10:03:56 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 6 Aug 2016 10:03:56 +0000 (UTC) Cc: clement.pit@gmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 06 12:03:52 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bVySG-0007AV-Qa for ged-emacs-devel@m.gmane.org; Sat, 06 Aug 2016 12:03:44 +0200 Original-Received: from localhost ([::1]:48684 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVySD-0002Vz-68 for ged-emacs-devel@m.gmane.org; Sat, 06 Aug 2016 06:03:41 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40835) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVyS4-0002Vf-CU for emacs-devel@gnu.org; Sat, 06 Aug 2016 06:03:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bVyS2-0004Mi-Cv for emacs-devel@gnu.org; Sat, 06 Aug 2016 06:03:31 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32795) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVyS2-0004MV-9L; Sat, 06 Aug 2016 06:03:30 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1828 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bVyS0-000640-CD; Sat, 06 Aug 2016 06:03:28 -0400 In-reply-to: (message from Stefan Monnier on Fri, 05 Aug 2016 22:11:55 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:206438 Archived-At: > From: Stefan Monnier > Date: Fri, 05 Aug 2016 22:11:55 -0400 > Cc: emacs-devel@gnu.org > > As I said elsewhere, I think this num-* side-condition can be dropped > because the inhibit-debugger variable should catch the same problems > but better. So maybe we should avoid entering the debugger only if _both_ variables say we shouldn't. That would be safer than just tossing num-nonmacro-input-events.