GNU bug report logs - #23471
Feature request: list all Edebug breakpoints

Previous Next

Package: emacs;

Reported by: Paul Pogonyshev <pogonyshev <at> gmail.com>

Date: Fri, 6 May 2016 17:51:01 UTC

Severity: wishlist

Tags: wontfix

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23471 in the body.
You can then email your comments to 23471 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#23471; Package emacs. (Fri, 06 May 2016 17:51:01 GMT) Full text and rfc822 format available.
Acknowledgement sent to Paul Pogonyshev <pogonyshev <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Fri, 06 May 2016 17:51:01 GMT) Full text and rfc822 format available.

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

From: Paul Pogonyshev <pogonyshev <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Feature request: list all Edebug breakpoints
Date: Fri, 6 May 2016 19:49:34 +0200

It would be nice to have a way to list all Edebug breakpoints in a
separate buffer, with an ability to jump to a breakpoint, see its
condition if any, and so on. Should probably reuse M-x next-error.
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#23471; Package emacs. (Sun, 20 Oct 2019 12:43:01 GMT) Full text and rfc822 format available.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Paul Pogonyshev <pogonyshev <at> gmail.com>
Cc: 23471 <at> debbugs.gnu.org
Subject: Re: bug#23471: Feature request: list all Edebug breakpoints
Date: Sun, 20 Oct 2019 14:42:40 +0200

Paul Pogonyshev <pogonyshev <at> gmail.com> writes:

> It would be nice to have a way to list all Edebug breakpoints in a
> separate buffer, with an ability to jump to a breakpoint, see its
> condition if any, and so on. Should probably reuse M-x next-error.

Hm...  I'm not sure I see the use case here.  Without some substantial
context (i.e., the surrounding code), a break point in itself would be
kinda hard to represent in a buffer.

And we have `edebug-next-breakpoint' to allow navigating to breakpoints.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) wontfix. Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sun, 20 Oct 2019 12:43:02 GMT) Full text and rfc822 format available.
bug closed, send any further explanations to 23471 <at> debbugs.gnu.org and Paul Pogonyshev <pogonyshev <at> gmail.com> Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sun, 20 Oct 2019 12:43:02 GMT) Full text and rfc822 format available.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 18 Nov 2019 12:24:09 GMT) Full text and rfc822 format available.
This bug report was last modified 4 years and 154 days ago.

Previous Next

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