GNU bug report logs - #77989
[PATCH] Use future history to select current script for pdb et al

Previous Next

To reply to this bug, email your comments to 77989 AT debbugs.gnu.org.

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

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

From: "Paul D. Nelson" <ultrono <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: [PATCH] Use future history to select current script for pdb et al
Date: Tue, 22 Apr 2025 17:01:18 +0200

[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)]

Previous Next

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