GNU bug report logs - #49675
28.0.50; minibuffer-quit produces error

Previous Next

Full log

Message #20 received at 49675 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Pankaj Jangid <pankaj <at> codeisgreat.org>
Cc: Gregory Heytings <gregory <at> heytings.org>, Eli Zaretskii <eliz <at> gnu.org>,
 49675 <at> debbugs.gnu.org
Subject: Re: bug#49675: 28.0.50; minibuffer-quit produces error
Date: Wed, 21 Jul 2021 16:20:48 +0200

Pankaj Jangid <pankaj <at> codeisgreat.org> writes:

> I could reproduce this with just
>
> (setq debug-on-error t)
>
> in my ~/emacs.d/init.el. The steps are:
>
> 1. emacs -Q
> 2. eval (setq debug-on-error t)
> 3. M-x C-g

Thanks; I can reproduce it with that recipe.  I think the problem may be
here:

static bool
maybe_call_debugger (Lisp_Object conditions, Lisp_Object sig, Lisp_Object data)
{
  Lisp_Object combined_data;

  combined_data = Fcons (sig, data);

  if (
      /* Don't try to run the debugger with interrupts blocked.
	 The editing loop would return anyway.  */
      ! input_blocked_p ()
      && NILP (Vinhibit_debugger)
      /* Does user want to enter debugger for this kind of error?  */
      && (EQ (sig, Qquit)
	  ? debug_on_quit
	  : wants_debugger (Vdebug_on_error, conditions))

I guess it should check whether it's an error symbol that inherits from
Qquit instead of testing for Qquit...  I'll take a poke at that and see
whether there's more of these.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.