unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 36145@debbugs.gnu.org, Xu Chunyang <mail@xuchunyang.me>
Subject: bug#36145: 26.2; Unable to "trigger another backtrace"
Date: Sun, 01 May 2022 13:41:53 +0200	[thread overview]
Message-ID: <87bkwho4xq.fsf@gnus.org> (raw)
In-Reply-To: <878rzos3yf.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 22 Sep 2021 23:19:52 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>>> And it's also possible to trigger another backtrace with 'e', if using
>>> it from a frame above the debugger's.  I bump into this every so often
>>> by accident, and it's quite annoying.  Of course, I'm always in the
>>> middle of debugging something else so I forget about it, but I'd like to
>>> change it.  Patch attached.
>
> Yes, that's super duper annoying, and it'd be really great to get that
> fixed.

I respun the patch, and observed that it did, indeed, not work, so I've
reworked it (instead of inhibiting the debugger, I just use
condition-case in these commands), and it now seems to work fine.  Oh,
and instead of having a prefix, I added a user option (both because I
think some people want to have the old action always, and because the
prefix was already taken in edebug now).

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





  reply	other threads:[~2022-05-01 11:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09  7:18 bug#36145: 26.2; Unable to "trigger another backtrace" Xu Chunyang
2019-06-09 12:19 ` Noam Postavsky
2019-06-09 15:50   ` Noam Postavsky
2019-06-21 12:21     ` Noam Postavsky
2019-06-21 12:50       ` Noam Postavsky
2021-09-22 21:19         ` Lars Ingebrigtsen
2022-05-01 11:41           ` Lars Ingebrigtsen [this message]
2022-05-01 11:07 ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87bkwho4xq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36145@debbugs.gnu.org \
    --cc=mail@xuchunyang.me \
    --cc=npostavs@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).