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

Previous Next

Full log

Message #10 received at 77989-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Paul D. Nelson" <ultrono <at> gmail.com>
Cc: 77989-done <at> debbugs.gnu.org
Subject: Re: bug#77989: [PATCH] Use future history to select current script for
 pdb et al
Date: Sat, 26 Apr 2025 16:22:16 +0300

> 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.

Previous Next

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