GNU bug report logs -
#77989
[PATCH] Use future history to select current script for pdb et al
Previous Next
Reported by: "Paul D. Nelson" <ultrono <at> gmail.com>
Date: Tue, 22 Apr 2025 15:02:01 UTC
Severity: normal
Tags: patch
Done: Eli Zaretskii <eliz <at> gnu.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 77989 in the body.
You can then email your comments to 77989 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#77989
; Package
emacs
.
(Tue, 22 Apr 2025 15:02:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Paul D. Nelson" <ultrono <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 22 Apr 2025 15:02:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
The simplest way I know to debug the current Python script is:
1. Copy the name of the current file (C-x C-j C-0 w)
2. M-x pdb RET yank RET (possibly after deleting previous file name)
This seems like a good place to introduce a "future history" operation.
The attached patch does so, via a new optional argument to
gud-query-cmdline. The above then simplifies to M-x pdb RET M-n RET.
Existing behavior is unchanged. I added the same feature to other gdb
commands for which it seemed to make sense (perldb, guiler). Feedback
or other suggestions would be welcome.
[0001-Add-forward-history-support-for-some-debuggers.patch (text/x-patch, attachment)]
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Sat, 26 Apr 2025 13:23:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
"Paul D. Nelson" <ultrono <at> gmail.com>
:
bug acknowledged by developer.
(Sat, 26 Apr 2025 13:23:03 GMT)
Full text and
rfc822 format available.
Message #10 received at 77989-done <at> debbugs.gnu.org (full text, mbox):
> From: "Paul D. Nelson" <ultrono <at> gmail.com>
> Date: Tue, 22 Apr 2025 17:01:18 +0200
>
> The simplest way I know to debug the current Python script is:
>
> 1. Copy the name of the current file (C-x C-j C-0 w)
> 2. M-x pdb RET yank RET (possibly after deleting previous file name)
>
> This seems like a good place to introduce a "future history" operation.
> The attached patch does so, via a new optional argument to
> gud-query-cmdline. The above then simplifies to M-x pdb RET M-n RET.
>
> Existing behavior is unchanged. I added the same feature to other gdb
> commands for which it seemed to make sense (perldb, guiler). Feedback
> or other suggestions would be welcome.
Thanks, installed on the master branch, and closing the bug.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 25 May 2025 11:24:26 GMT)
Full text and
rfc822 format available.
This bug report was last modified 42 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.