[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23470: Feature request: preserve breakpoints when C-u C-M-x function
From: |
Eli Zaretskii |
Subject: |
bug#23470: Feature request: preserve breakpoints when C-u C-M-x function definitions |
Date: |
Sun, 20 Oct 2019 14:11:09 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 20 Oct 2019 12:41:47 +0200
> Cc: 23470@debbugs.gnu.org
>
> Paul Pogonyshev <pogonyshev@gmail.com> writes:
>
> > When I re-evaluate (C-M-x) a function definition that has breakpoints,
> > all of them are lost. This is particularly annoying when breakpoints
> > are conditional, because now I not only have to recreate them
> > manually, but also specify all the conditions again.
>
> Yes, that sounds useful.
>
> > Request: preserve existing breakpoints within definitions where
> > possible. One idea suggested on the devel list is to assign a marker
> > to each breakpoint and recreate it at the new marker position when
> > re-evaluating, as long as marker is not deleted (related to
> > bug#23468).
>
> Hm... is that necessary? The breakpoints are tied to the offsets...
> Hm, yes, but I guess the offsets will change if you've added/removed
> some forms, which would put the breakpoints at the wrong position. So
> markers seem like a better solution.
If this request is implemented, how will the user be able to cancel
all the breakpoints in a function?