all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Jean Louis <bugs@gnu.support>
Cc: 37352@debbugs.gnu.org
Subject: bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation
Date: Sun, 22 Sep 2019 09:14:21 -0700 (PDT)	[thread overview]
Message-ID: <e29ffec8-666d-4174-9a08-f20343d9b176@default> (raw)
In-Reply-To: <87woe0v3tl.fsf@gnus.org>

> I don't know why the `q' command in the debugging mode
> is defined that way.

Uh, because it makes sense?  The recursive edit
was entered only for use of the debugger.

What is the real problem that this bug report is
trying to report?  What's the aim?  (Sounds like
an X-Y question.)





  reply	other threads:[~2019-09-22 16:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  7:41 bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation Jean Louis
2019-09-20 18:30 ` Lars Ingebrigtsen
2019-09-20 19:09   ` Jean Louis
2019-09-20 21:01     ` Lars Ingebrigtsen
2019-09-22 12:57       ` Jean Louis
2019-09-22 13:00         ` Lars Ingebrigtsen
2019-09-22 13:04           ` Jean Louis
2019-09-22 13:49             ` Lars Ingebrigtsen
2019-09-22 16:14               ` Drew Adams [this message]
2019-09-22 16:39                 ` Noam Postavsky
2019-09-22 16:55                   ` Drew Adams
2019-09-22 16:59                   ` Eli Zaretskii
2019-09-22 17:54                     ` Andreas Schwab
2019-09-22 18:20                       ` Eli Zaretskii
2019-09-23 10:18                         ` Lars Ingebrigtsen
2019-09-23 12:43                           ` Noam Postavsky
2019-09-23 14:01                             ` Lars Ingebrigtsen
2019-09-23 14:14                             ` Andreas Schwab
2019-09-25  8:11                           ` Eli Zaretskii
2019-09-25 13:09                             ` Lars Ingebrigtsen
2019-09-22 16:58                 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e29ffec8-666d-4174-9a08-f20343d9b176@default \
    --to=drew.adams@oracle.com \
    --cc=37352@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.